On Fri, Sep 15, 2006 at 09:01:12AM -0600, Chris Kuethe wrote:
> 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.
That depends on setup, but I believe that you are right and I
misunderstood.
If the mfs on /var is mounted before syslogd and crond start up, you are
of course, right - and I believe this is what we should be talking
about. In this case, disregard my post.
I was thinking of the case where one starts the system, and only then
changes /var. In this case, problems with syslogd and crond would arise.
However, in retrospect, this would not be a very sensible thing to do.
Sorry for the noise!
Joachim
