[rbldnsd] rbldnsd and logrorate?

[Per Jessen]

Michael Tokarev wrote:

> It's not logrotate&rbldnsd, it's syslogd&rbldnsd.  The thing is like
> this:
> 
>  rbldnsd opens the log socket (/dev/log) on startup before entering
>  chroot jail. Inside the jail, there's (usually) no /dev/log exists.
>  Some implementations of syslogd performs - for whatever reason -
>  re-creating of
>  the log socket on reloads.  So the socket opened by rbldnsd becomes
>  invalid, and rbldnsd (actually it's glibc implementation of
>  syslog(3)) tries to re-open it on
>  next message, but fails because in the chroot jail there's no
>  /dev/log.  And hence it just stops logging.

Ah. Thanks for the explanation.

> The fix is to find out why syslogd re-creates /dev/log socket, and
> stop it from doing that. 

I'm using syslog-ng - I'll check with the people over there. 

> Another (less good but still acceptable) fix is to tell syslogd to
> keep another log socket inside rbldnsd chroot directory. 

Thanks, that'll do temporarily. 


/Per Jessen, Zürich