Heiko Zuerker wrote:
> On Mon, February 26, 2007 15:23, Dick Middleton wrote:
>> Heiko Zuerker wrote:
>>
>>> On Sun, February 18, 2007 17:21, Dick Middleton wrote:
>>>
>>>> I've just realized that named logging stops after logrotate reloads
>>>> syslog-ng. I have to restart named to restore named logging.
>>>>
>>>>
>>>> I'm not too sure how named communicates with syslog but I guess this
>>>> is a jail problem.
>>>>
>>>> Anybody else have this problem or perhaps an explantion? Maybe I'm
>>>> missing something from my named.conf (which has no logging options set
>>>> i.e. uses defaults).
>>> Which version of DL are you on, since we changed the jail behavior a
>>> while ago?
>> 1.2.11
>>
>>
>> It seems to be to do with /dev/log not being connect to syslog after
>> syslog is restarted.
>
> Yeah that would explain it.
> I think we should avoid restarting syslog-ng, I got to look into it.
logrotate has a copytruncate option which can be used to avoid restarting the
app. It works fine and resolves this problem for normal operations. I've
changed most of the logrotate scripts to use it anyway.
However it doesn't fix the underlying problem. I'm thinking, FWIW, that having
a tempfs for jail communicating sockets which can be bind mounted where it's
needed might solve these problems.
Dick
|
