Hot answers tagged debian-lenny
You can use the following sources until you upgrade your system: deb http://archive.debian.org/debian/ lenny contrib main non-free
modify your /etc/apt/sources.list as follows: deb http://archive.debian.org/debian/ lenny main contrib non-free deb-src http://archive.debian.org/debian/ lenny main contrib non-free deb http://archive.debian.org/debian-security lenny/updates main contrib non-free deb-src http://archive.debian.org/debian-security lenny/updates main contrib non-free deb ...
lenny is superseded by squeeze, and its lifecycle ended on Feb. 6th this year. You'll get no updates from the core Debian community for lenny. Options: Upgrade to squeeze. Stay with lenny, remove the Debian FTP servers from sources.list and keep the packages as they are. There will be no security updates. Pin (man apt_preferences) necessary packages down ...
The "stop" term does not prevent the daemon from starting but rather shuts it down while entering the specified runlevel. If you just want to remove a service/daemon from a single runlevel, update-rc.d as pointed out bei freiheit or simply remove the symlink from /etc/rcX.d/, where X is your runlevel. If you don't want the service to start automatically, ...
apt-get install sysv-rc-conf As others have pointed out, here is also update-rc.d for the cmd line. Run update-rc.d apache2 disable to disable apache2 from all run levels.
You can create your daemon manually following the /etc/init.d/skeleton file on Debian. You can use /usr/bin/service to launch $ sudo service yourdaemon start and sstop $ sudo service yourdaemon stop your daemon. As long as you do not link your script to any of the /etc/rc?.d directories, it won't get started on startup. On the other hand, you may want to ...
From a little poking around, it appears to be a problem with the Debian mirrors. According to the mirror info, lenny should be available, although you might need to change each instance of 'lenny' with 'oldstable' in /etc/apt/sources.list. However, pulling up 3 mirrors have all shown that 'lenny' and 'oldstable' are no longer listed. Update: I did a ...
archive.debian.org has the package repositories of all EOLd debian releases
If you're using bash (default shell in Debian) you can see all your recent history in the file ~/.bash_history (so .bash_history file in your local user) Also from the command line you can type history and it'll also show you all your recent command history
The package you most likely want is git-core. (Works just fine without adding an extra repository.) Update: This has now been fixed; in squeeze and beyond the git package is now called git.
Since a repository is not a single file but a directory structure (conf, dav, db, ...) you might want to use rm -rf /path/to/directory
The file you want is: /root/.bash_history
Deleting the log files alone won't help. You need to tell the daemon to close the log file, usually by sending it a SIGHUP. logrotate should be handling the logs, and it can use various criteria to determine when the log should be rotated. Your logs are filling up awful fast. Either figure out what's flooding your logs, send your logs to another machine for ...
Yes, adding a new non-root user, then sudoing from it is the "best-practice". If you have a lot of commands to run at once many people say to run sudo su -. However, sudo has a -i option that is used to give you a root shell. Also, if you want to disable interactive logins for root, you can change the password in /etc/shadow to '!'. To have two users ...
Not really sure if you can create a user which doesn't have a home directory specified. That being said, the specified home directory doesn't have to exists. You can call the adduser with the option --no-create-home. adduser --no-create-home foo (adduser is usually the preferred higher level tool if called interactively.)
For me that looks good. Your PHP + MySQL is taking only around 100 megabytes of RAM, leaving lots of room for the operating system to breathe. For your "how many users this VPS can handle?" question: it depends. With proper caching and other best practices I think it should handle at least dozens of requests per second, if not more. If the content is ...
It isn't good, your php5-fpm process take around 35Mo. With this configuration you may have 50 process (max_children = 50), with each one of them allocating 35mo. thus, your machine which have only 512Mo will swap. I think that your limit is around 10 process of php-fpm (max_children = 10).
It might happen because curl can't access valid CA certs bundle. Maybe you just didn't install those, so try this: apt-get install ca-certificates If it doesn't help - check CURL_CA_BUNDLE, make sure curl doesn't look for bundle in a wrong place.
Install devscripts Get the patch for lenny from http://pastebin.com/Hhsut197 (based on the official glibc patch, removed ChangeLog, NEWS stuff, adapted Makefile for lenny, removed patch #2 for getXXbyYY_r.c) Run: apt-get update && apt-get source libc6; apt-get build-dep libc6 Copy your patch in glibc-2.7/debian/patches/all Add the patch name in ...
I'm assuming that you have two VirtualHosts: VH for WP that hosts *.mydomain.com VH for independant webiste that hosts subdomain.mydomain.com Make sure that your subdomain.mydomain.com VirtualHost is loaded or located in file before the VirtualHost with ServerAlias of *.mydomain.com. Apache will use the 1st VH it finds that matches ServerName/Alias. ...
Okay, I think the answer is that the COW space for the logical volume is full. Using the command 'lvs' (which I just discovered), I see... # lvs /dev/dm-20: read failed after 0 of 4096 at 0: Input/output error LV VG Attr LSize Origin Snap% Move Log Copy% Convert [...other LVs...] newvm-cdrive mrburns Swi-I- 2.00G ...
Short: There is no reliable way to do this quickly. Long: Current Debian (Debian unstable as of 2012-06-01) has currently no reliable short way to consistently disable a service/daemon. – Because an upgrade of a daemon package unconditionally runs “/etc/init.d/package restart”, having it disabled for this runlevel or not. To make sure a daemon doesn’t ...
A faulty DNS record should only have impact on name resolution, not pure IP communication and would not have any interference with a router. One bad zone file can prevent the entire DNS server from running, at least with Bind I've experienced this. So I could see you having issues with name resolution if this is your primary DNS server your workstation is ...
There is a better solution than m-a: dkms It actually makes it easier to distribute external kernel modules and automatically compiles them for newer kernel-versions (think installing a new package of linux-headers).
To get ~1.7.1 use this method. If you want ~188.8.131.52 then use andol's answer. This is because git is a dummy package in Lenny which provides gnuit. Package: git (4.9.4-1) However, you can get around this by using the lenny-backports git package: UPDATE: As of September 5th 2010, this method has changed slightly as backports.org is being phased out the ...
I'm answering my own question because I wanted to know how to solve the problem while using the new slapd.d/dynamic/cn=config backend and I didn't wanted going back to the slapd.conf method. (Almost nobody is doing this, AFAICT) When I try to add the new schema using ldapadd, I was always getting the following error: ldapadd -H ldap://whatever.test.com -D ...
You can run lsof | grep deleted and check witch programs allocated this space (and the deleted file). example: [root@mab-01 ~]# lsof | grep deleted hald-addo 2651 haldaemon txt REG 253,0 15720 3769183 /usr/libexec/hald-addon-keyboard.#prelink#.IhBW5L (deleted) yum-updat 2899 root txt REG 253,0 ...
On the machine A: ssh -L 3307:C:3306 user@B This allocated a socket listen to port 3307 on A. And whenever a connection is made to this port, it is forwarded over ssh tunnel to C:3306. You can then connect to MySQL server on C with: mysql -u <user> -p -h 127.0.0.1 -P 3307 (127.0.0.1 to connect via TCP/IP instead of a socket) No, I cannot ...
You can: Update your distro See if backports has the version you need and add lenny-backports to your apt Get the source package and rebuild it on your server (or on a Lenny machine, wich is more safe) Add squeeze repository to apt sources, then add the APT::Default-Release option to apt configuration and ask to install the new version. I will not describe ...
Only top voted, non community-wiki answers of a minimum length are eligible