On 9/15/06, Joachim Schipper <[EMAIL PROTECTED]> wrote:
Certainly, daemons chrooted in /var/empty won't be able to use syslog and there will be something wrong with cron (maybe the notification to re-read changed crontabs?).
Bunk! Syslogd will create extra/alternate sockets when it starts up, provided that you tell it to do so with "-a". And cron will create its notification socket. Both of these behaviours can be found by a quick grep in the source, and the syslogd manpage explicitly mentions the use of "-a" to put log sockets in chroot jails. CK -- GDB has a 'break' feature; why doesn't it have 'fix' too?
