I would like to run a mailing daemon on my system that would receive incoming mail and forwards it to my Gmail account. I have no experience in mail services and forwarding mail at all. where to start reading and/or look for clues?
I'm trying to set up a small web server with php and sqlite support. I installed lighttpd, php5, php-sqlite3 and php5-sqlite3. Then, I enabled sqlite and pdo extensions in php.ini: extension=pdo.so extension=sqlite.so extension=pdo_sqlite.so
However, when I try to open a SQLite3 database from php: $database = new SQLiteDatabase($myDB, 666, $error); I get the following exception: SQLiteDatabase::__construct() [sqlitedatabase.--construct]: file is encrypted or is not a database
Some readings in the net make me think that my php settings are not compatible with SQLite3 databases. Is anyone successfully working with SQLite3 databases from PHP5 under Debian? Have you any recommendations? Should I rebuild php maybe?
I am putting together a server and computer lab at my school for Standardized testing, and am planning on using debian for it. But first, i must prove to the school board that this is a possible and viable option, so right now it is one pc with 1 gig ram (Going to be the server for this experiment), and two others with around 512 mb ram.the problem with all this is, the computers in the lab cannot have hard drives, as there is some sort of licencing issue. So I need to be able to have these two testing computers boot from the server's hard drive.
I have 2 windows pc's in my home and an office computer that have my files strewn about. I wanted to have them all in one central location that keeps a backup copy, so i used an old machine to start building a file server. I installed debian 5.0 on the machine, command line interface only. I have gotten ssh working so that i can do all my work on the box from one of my windows pc's by logging in with putty.my current problem is how to easily use the box hard drive for storing my files in an easily accessible way. i'm still working on getting samba to work so that i could map the /home directory to a drive letter on my two home pc's, but i'd also like to access files from my work pc. Before i do that, though, i wanted to know if this is safe and secure to map a drive on a remote machine through the internet? Are there any other security concerns I need to be addressing by having this file server set up?
I'm a beginner + in debian (ie I know how to launch basic command under a shell), and I very new to configuration problem.I have a running perfectly file server for probably more than 2 years that I never touch. That's the debian problem, when it's unning, it's forever, no reboot at all.I recently bought 2 new sata drive 1TB5, that I add to my system by adding to my old system a SATA PCI board without any problem.But, one of these 3 month old drive is already dead.So I try to replace it and that's where problem started.....First I did a#mdadm --manage /dev/md1 --remove /dev/sdb1, of course without sucess because sdb is dead
#mdadm --detail /dev/md1 /dev/md1: Version : 00.90.03
I have a home Debian server running, and i would like to set it up as a gateway. I have 2 networkcards in it. So internet comes from the modem and on the other card i want to setup a dhcp server and it has to share the internet. But i want it also to connect to a vpn and share the internet of the vpn.. Is that possible?
Recently tried to make RAID1 on MBR partitions scheme on Debian Jessie - debian-8.1.0-amd64-DVD-1. The issue - I have unable to boot from second drive after grub-install /dev/sdb by any ways. RAID1 itself for / swap and home is fully functional. Decided to try the same thing on GPT, same story. How to boot from second drive on most recent Debian Branches?
Alright, first Squeeze wouldn't create an initial RAM disk even with "--initrd" specified. Now I don't need one and it's creating one for me even though I don't want one! How do I stop this? I'm beginning to feel like I am using Windows in the sense that it's doing things on its own. Don't make me a RAM disk unless I say so!
i would like to prevent all users other than the user "parker" on my system from using the su or sudo commands. I have not attempted to modify the sudoers file so it just contains the standard root ALL = (ALL) ALL.
I have a PC that have a new Ethernet card that is not yet supported by Debian/Lenny.I downloaded the latests driver from the manufacturer and after a make;make install everything works like a charm.My problem is that one day after a probable update, Debian overrided my new driver by an other one causing my Ethernet card to shut down.After an other make install, everything work again like it should..But how do i do to prevent Debian to update my driver ?
I'm trying to prevent GDM/Gnome from turning the screen off prior to login. It's current behavior, under 3.14, slowly fades the screen out and then enters DPMS mode after 10 minutes.I have zeroed out the following dconf settings, under both root and user, but the default behavior persists.
I installed a raid1 on a debian lenny box with only 1 drive "--raid-devices=1" because I didn't have the other drive yet. When I got the other drive, I used "mdadm --grow /dev/md0 --raid-devices=2" and "mdadm --manage /dev/md0 --add /dev/sdb1" The original drive is sda1. I watched /proc/mdstat until it was completely synced, and after a reboot, the system will not reassamble the raid. It fails with "mdadm: no devices found for /dev/md0" This is where root is, therefore, I get nowhere. From a rescue cd I can disable the other drive and shrink back down to 1 device and it boots fine.
I'm building a NAS with xubuntu and I've put 2x1,5TB disks in RAID1 with mdadm. My question is really straightforward: do you have any advice for some special tuning/configuration for the RAID setup? Somewhere I read that I should disable disk caching, but I would like to have some more opinions.
I have two ethernet NIC's on my debian server. One built-in Realtek [eth0] (attached to internet), and a PCI Nvidia ethernet card [eth1] (attached to my Win7 netbook). I used this guide to setup the bridge: url. It worked when I was behind a router. But when I moved the computer in front of the router, to direct connect to the internet, the internet stopped functioning on any device that I plug into my Nvidia NIC. The name of my bridge is 'br0'. Does anyone know how to fix it, so I can route the internet to my second NIC?
My Win7 netbook displays this at an 'ipconfig' command: Windows IP Configuration
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo br0 iface lo inet loopback # Set up interfaces manually, avoiding conflicts with, e.g., network manager iface eth0 inet manual iface eth1 inet manual # Bridge setup iface br0 inet dhcp bridge_ports eth0 eth1
I just installed Debian 6 squeeze on a P3, 632 MB RAM, 20 GB HD, and am trying to get it on-line. Ran lspci and lsusb on it (advice from another forum). Got the following results:
Exactly what I am trying to do: Existing network is as follows: Comcast internet to cable modem to Belkin N Wireless Router Model F5D 8236-4 v3. That router is wired to one desktop (running Windows XP)and has 4 wifi notebooks (two running Windows 7 and two running Mint 9 Isadora) and two Wii consoles running off of it. I am seeking to add another desktop to the network in another room without having to drill some holes and run about 40 feet of cable. Seems like it shouldn't take much to get the two routers to "talk" to each other so I can do this. The router I am trying to hook to it is either a Belkin F5D 9230-4 wireless router or a NetGear N150 WNR1000 v2 Wireless router.
setting up NAT and firewalling for both IPv4 and IPv6. The machine is headless, so everything must be configured via CLI. I've done all IPv4 firewall configuration writing iptables rules in a bash script so far
I am trying to figure out what needs to be done to automatically set read/write permissions for everyone for my proprietary USB device on system boot. I have created a udev rules file which changes the permissions for the device when it is connected, but it does not change the permissions when the system is booted with the device already connected. The file looks like this:
Would like to know the best way (or the pros and cons of different ways) to set up Alsa. I did a search for information on how to setup alsa on my system. I found a lot of out-of-date information even on the alsa wiki. What I did finally locate was two different methods for setup, both seemed somewhat up-to-date. One method at the alsa wiki said to put part of the information in the modprobe directory in a conf file and set up certain aliases. Earlier suggestions for putting information in modprobe.conf or conf.modprobe appear to be outdated and a directory with separate files for each device and a conf extension to the files is currently used. The second method from a thread on the Debian forum said to use alsactl init, set sound levels the way you want and then use alsactl save and restore functionality. Older methods using alsaconf instead of alsactl init appear to be outdated as well. Not sure where to put the call to alsactl restore though. Didn't notice that in the documentation.In case it matters, I'm running Debian Stable and have a built-in sound card on the motherboard with AC97 compatibility. It's a Realtek ALC882.
Is there a preferred or better method for setting up alsa? Is there a good pointer to instructions that are not out-of-date somewhere? Would be very interested to hear how others set sound up on their machines. What do others recommend as best steps to do this?
New to linux in general and am having issues on setting up a Raid 1 array for two disks on an HP Proliant Microserver which I am looking to be accessible from my windows PC. I have installed the latest version of debian succesfully on a 250GB disk that came with the server. I have added 2 2TB disks which I would like to have in a RAID 1 array and to have visible from windows to store music/videos etc on. I have managed to partition the two disks to FAT32 (which I think is best) and have managed to configure the array so that it shows as active when I use cat /proc/mdstat. I have been following the steps in this article [URl]... squeeze-p2 and trying to adapt it to my situation.
I am stuck on the step to create the file systems using the mkfs command. I try mkfs.vfat /dev/md0 and it comes up with the error mkfs.vfat: command not found. I have tried mkfs -t vfat /dev/md0 and it give the error "mkfs.vfat: No such file or directory" So my question is how can I continue with the process of setting up the array? Or maybe I should be asking is it possible to set up an array with FAT32 formatted disks?
Setting up my Squeeze test box, I can't seem to get APache2 to find index.html. It keeps coming up with the initial "It works!" page.
On my Squeeze server, the /etc/apache2/httpd.conf file contains this line: DocumentRoot /home/www_local and that box serves the website perfectly.
On the test box, I created the /home/www_local directory and put an index.html file in it, then populated /etc/apache2/httpd.conf with exactly the same DocumentRoot line and restarted Apache. Still the same result -- Apache isn't finding my index.html file. I have grep'ed all the files in /etc/apache2 and /etc/apache2/conf.d looking for 'DocumentRoot' and it's not in any of them.
I'm intending to replace my current router (486DX2 w/16MB running FREESCO which has been faithfully working 24/7 for well over a decade) with a debian box with a bit more grunt and newer features. I'm currently setting up my iptables ruleset and am after a bit of advice re the FORWARD policy. A few example rulesets I have found set the default policy to DROP and the have two lines for each port forward, one to allow the traffic and one to direct the incoming packets to the correct machine.
I'm thinking of setting the default policy to ACCEPT to cut down on typing as my default INPUT policy is DROP and unless there is a valid FORWARD rule for a particular port, the packets aren't going anywhere anyway. Or have I misunderstood something. My googling returned heaps of example scripts & not much intelligent commentary. Alternatively, what do you all use to configure & maintain your debian gateways; hand rolled iptables rules, or any toolset recommendations?
I have installed the Nvidia drivers on my desktop using [URL] according to the Debian way. Everything seems to be fine except the resolution. The best it will let me choose is something like 600x480. I have searched and most of what is suggested around the web is to change xorg.conf. I have tried this using different setting suggested but nothing is working. I did not have a xorg.conf file so I created one with the setting suggested on the Debian wiki.
I have Debian 8.2 with KDE 4.14 and everything runs perfect, except for the internet connection. This problem happens randomly when I turn on my machine. Sometimes when the desktop loads, the connection is already settled.
But sometimes when the desktop loads, the wifi icon is still loading and keeps stuck at "setting network address". Since this problem happens randomly I really don't know what is happening here. My wifi chip is this:
Since I got the liquorix kernel installed on my machine I got an error of setting kernel variable error. net.ipv6.bindv6only at boot time, since it wasnt a big deal I never looked further into it, but now that I had some spare time and I didnt want to see any errors on my machine I found a solution for it, with a little googling all we need to do is read the /usr/share/doc/procps/README.Debian and bingo no more error i hope this help anyone else with the same problem. I did the 3rd suggestion on that file to load the module in /etc/modules cheers.
how to get clients connecting to an office printer. during a migration from windows server to debian/samba.
5 windows XP machines one Windows Server 2003 machine, PDC of the old domain One debian Samba PDC (of TEST domain)/print server (with CUPS installeD) running in a virtual machine hosted by the windows server One Toshiba eStudio 3511 printer
Using the CUPS control panel, I've been able to autodetect and add the printer, and it appears as an available share in SWAT for samba. However, the driver isn't perfect. CUPS could only supply drivers for the 3510c, not the 3511.
However, clients on the TEST domain are unable to access it. Doing so gives an error about a local policy preventing a connection to the print queue. I've tried googling this error and the fix that comes up in every result about changing a point and print policy setting, does not work.
however, I've been able to work around the issue. by first logging in as local administrator, navigating to the domain server, then inputting the domain root account credentials at the prompt. That allows me to attempt to connect to printers, but with a different error
"The server for the printer does not have the correct driver installed...."
I very strongly suspect that the 3510 driver actually will work, but it's just not being shared properly. The printer driver share folder is /var/lib/samba/printers, and that directory contains only a few empty subfolders. CUPS did not place the driver there as I would expect, and that is where clients are looking for it.
The thing is, I have no idea where CUPS DID put the driver.
On the old domain, the printer uses drivers for es4511, and looking on the toshiba site, this seems to be what they provide. The Toshiba Site provides a huge variety of drivers, including several windows ones, a universal driver, and a CUPS PPD. Cups asks for an optional PPD during install and I tried supplying that. It said installed successfully, but didn't change anything.
I've tried pasting the windows drivers into /var/lib/samba/printers/W32X86 too, and likewise with other drivers from toshiba's site. but this doesn't change anything either, so I'm at a bit of a loss.
how to install/setup drivers on a samba PDC, for windows machines?
Also relevant, my smb.conf: anyone see any possible causes of problems? # Samba config file created using SWAT # from UNKNOWN () # Date: 2010/08/19 13:03:07
Despite having the Gnome Power Manager set to put the display to seep after 30 minutes, it always happens after 5 minutes. The display will go blank but still lit, and then it powers off after the 30 minutes. Surely, if I set it to 30 minutes, the display should power off then, and not just blank after 5? I have no screensaver packages installed so it's nothing to do with that.