Package: sysklogd
Version: 1.4.1-21ubuntu3
Severity: normal
File: syslog


/etc/init.d/sysklogd reload behaves different from /etc/init.d/sysklogd restart
in that files that receive logs, and that are not directly below /var/log, but
eg. below /var/log/news stop logging on reload. only restarting sysklogd will
make it open and write those files again.

to test do below commands and compare the directory listings:

/etc/init.d/sysklogd restart
ls -l /proc/$(cat /var/run/syslogd.pid)/fd
/etc/init.d/sysklogd reload
ls -l /proc/$(cat /var/run/syslogd.pid)/fd

peter


-- System Information:
Debian Release: lenny/sid
APT prefers gutsy-updates
APT policy: (500, 'gutsy-updates'), (500, 'gutsy-security'), (500, 'gutsy')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-14-server (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysklogd depends on:
ii adduser 3.103ubuntu1 Add and remove users and groups
ii klogd [linux-kerne 1.4.1-21ubuntu3 Kernel Logging Daemon
ii libc6 2.6.1-1ubuntu10 GNU C Library: Shared libraries
ii lsb-base 3.1-23.1ubuntu3 Linux Standard Base 3.1 init scrip
ii sysv-rc 2.86.ds1-14.1ubuntu31 System-V-like runlevel change mech

sysklogd recommends no packages.

-- no debconf information

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users