>From: SZALAY Attila <[EMAIL PROTECTED]>
> On Wed, 2005-09-07 at 00:02 -0700, Elliott Mitchell wrote:
> >
> > If /dev is read-only, syslog-ng will give the error message
> > "syslog-ngio.c: bind_unix_socket(): bind failed /dev/log (Address already
> > in use)". The relevant section from `ltrace -LSf`:
>
> The problem is, that a sysklogd do just the same. Could you please send
> an ltrace of sysklogd in the same situation.
>
> Look at this:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84204;archive=yes
Hmm. Sounds very familiar.
After much research...
I thought there was a way to reuse sockets without having to unlink() the
old one. Looks like I was wrong. The observation that SO_REUSEADDR should
work for AF_UNIX sockets seems to be shown again. :-(
Looks like sysklogd indeed likely fail to setup the socket, and as Bernd
Eckenfels observed simply continues doing the rest of its job. This means
in their default configuration running syslog-ng/sysklogd *requires* /dev
to be writable. I believe this qualifies as a policy (possibly FHS?)
violation. Seems that /dev/log should be a symbolic link to a socket in
/var/run, which *will* be writable. This then becomes an error with the
default configuration.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | [EMAIL PROTECTED] PGP 8881EF59 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
\___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
