[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#3103: "/etc/init.d/sysklogd restart" does not restart klogd



Package: sysklogd
Version: 1.3-4

"/etc/init.d/sysklogd restart" does not restart klogd. The same thing
happened to me when I upgraded sysklogd from 1.3-2 to 1.3-4 with dpkg.
Here's a transcript of a session:


[...]
Installing new version of config file /etc/cron.weekly/sysklogd ...
Version 1.3 of the package is the culmination of about two years of
experience and bug reports on the 1.2 version from both the INTERNET
and our corporate Linux networks.
The default behaviour of syslogd has altered from 1.2 to 1.3. By default
*no* messages from the UDP port are accepted.
Read the documentation in /usr/doc/base/sysklogd carefully. Some important
things have been changed!
starting /sbin/syslogd ...
starting /sbin/klogd ...
klogd: Already running.                       <----- HERE

12:03 [root:p0] thot:~# ps aux | grep logd
root     19938  0.0  1.5   928   488  ?  S    11:26   0:00 /sbin/klogd
root     20116  0.1  1.4   844   444  ?  S    12:03   0:00 /sbin/syslogd
root     20121  0.0  1.1   912   372  p0 S    12:03   0:00 grep logd

12:03 [root:p0] thot:~# /etc/init.d/sysklogd restart
stopped process in pidfile `/var/run/syslogd.pid' (pid 20116).
stopped process in pidfile `/var/run/klogd.pid' (pid 19938).
starting /sbin/syslogd ...
starting /sbin/klogd ...
klogd: Already running.                       <----- HERE

12:04 [root:p0] thot:~# ps aux | grep logd
root     20128  1.5  1.3   840   436  ?  S    12:04   0:00 /sbin/syslogd
root     20131  0.0  1.1   912   372  p0 S    12:04   0:00 grep logd

12:04 [root:p0] thot:~#     start-stop-daemon --start --verbose --exec /sbin/klo
gd
starting /sbin/klogd ...                      <---- HERE

12:07 [root:p0] thot:~#


If, instead of running start-stop-deamon on klogd myself, I had rerun
/etc/init.d/sysklogd it would have also started correctly.

Apparently the old klogd is not dead yet when start-stop-daemon runs,
maybe a 'sleep' between the kill and the restart would solve this.

--
Farzad FARID
Administrateur Reseau
SGIP - Publicis



Reply to: