On Wed, Sep 05, 2001 at 01:20:26PM +0200, Eric Romang wrote:
Hello,
For DHCPD, my ps -aux give me this :
root 611 0.0 0.2 1364 636 ? S 13:13 0:00 /sbin/syslogd -a /var/lib/dhcp/var/run/dhcpd.pid
Why DHCPD has an process with syslog ??
syslogd has been started to listen on the socket /var/lib/dhcp/var/run/dhcpd.pid in addition to /dev/log. This (see below) socket would be useful for a dhcpd process that runs in an chroot environment with root=/var/lib/dhcp/. This is wrong in two ways: You (or whoever) has added this to SYSLOGD_PARAMS in /etc/rc.config. The first mistake is that the socket should be /var/lib/dhcp/dev/log and not /var/lib/dhcp/var/run/dhcpd.pid. Note, that this is not the default on any SuSE Linux, and someone has added this manually! The second mistake is that you neither need the additional socket (since you are not running dhcpd), nor you do you want it. Check SYSLOGD_PARAMS in /etc/rc.config!
I don't have lunch DHCPD on startup... I don't wan't dhcpd... In my rc.concfig START_DHCPD is set to no... but they are some pid ...
An old pid file might have been left by dhcpd. Sometimes, if it won't start due to incorrect syntax of dhcpd.conf, it leaves the pid file. You can safely delete it. Also, if you play with DHCPD_RUN_CHROOTED in dhcpd.rc.config while dhcpd is running, this can happen. Don't worry.
But I don't understand why my server freeze whitout reason...
Me neither, I only wanted to comment on the dhcpd issue. Peter -- Peter Poeml poeml at suse.de ------------------------------------------------------------------------------- VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...