On Sun, Jun 15, 2008 at 05:11:43PM -0400, Robert Edmonds wrote: > I can reproduce the problem with sysklogd... I based the debian init > script on the redhat one provided in the unbound tarball, which > bindmounts /dev/log to /var/lib/unbound/dev/log. unfortunately since > /dev/log is a unix socket, it disappears and is recreated when the > syslog daemon is restarted, and the bindmount follows the inode rather > than the directory path.
i thought it would be something like that. > just to verify, could you send the output of `stat /dev/log > /var/lib/unbound/dev/log | grep Inode` before and after a restart of > unbound? it probably looks something like this: sorry, i did this but forgot to copy the output. it WAS the same as in your example. inodes different before restart, same afterwards. > now, could you please test this solution? > > 1) /etc/init.d/unbound stop > > 2) echo "$AddUnixListenSocket /var/lib/unbound/dev/log" > > /etc/rsyslog.d/unbound.conf > > 3) /etc/init.d/rsyslog restart > > 4) replace /etc/init.d/unbound with the copy attached to this mail > > 5) /etc/init.d/unbound start OK, done. that seems to fix the problem. unbound keeps on logging no matter how many times i reload rsyslog. given that there are several different syslog daemons available in debian, probably the best "fix" to this problem is to have a README.Debian file detailing what needs to be done for each different syslog daemon. the important thing is that the issue and the known work-arounds should be documented. craig -- craig sanders <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
