Package: sysklogd Version: 1.5-3 Severity: normal Hi,
On upgrading sysklogd and klogd from 1.5-2 to 1.5-3 inside a Sid chroot, I get the following: > Setting up klogd (1.5-3) ... > Installing new version of config file /etc/init.d/klogd ... > Stopping kernel log daemon... failed! > Starting kernel log daemon.... > ln: creating symbolic link `/lib/init/rw/sendsigs.omit.d/klogd': No such file > or directory > Setting up sysklogd (1.5-3) ... > Installing new version of config file /etc/init.d/sysklogd ... > Stopping system log daemon... failed! > Starting system log daemon.... > ln: creating symbolic link `/lib/init/rw/sendsigs.omit.d/sysklogd': No such > file or directory The only thing responsible for creating the sendsigs.omit.d directory is apparently /etc/init.d/mountkernfs.sh, which of course is not run from within the chroot. Would it be possible for the sysklogd and klogd postinsts to try to create this directory if it does not already exist, before creating symlinks inside it, in order to account for the possibility that they are running inside a chroot? I'll clone this bug against klogd as soon as I get a bug number back, since it applies to both binary packages. Thanks and best regards, -- Kevin B. McCarty <[EMAIL PROTECTED]> WWW: http://www.starplot.org/ WWW: http://people.debian.org/~kmccarty/ GPG: public key ID 4F83C751
signature.asc
Description: OpenPGP digital signature
