On 30 May 2003, Jarno Gassenbauer wrote:

> P.S.: It's a pity that the syslogd socket is located
> at /dev/log and not in an own directory. A hardlink to
> /dev/log would have to be recreated after restarting
> syslogd. Mount-binding the whole /dev directory into
> the jail isn't fun either.

You can have syslogd listen on additional sockets with the -a <socket>
option. Multiple -a options are allowed. This is great for chroot's.


Reply via email to