Rocco Scappatura wrote:
>>>
>>> /var/log/cbpolicyd.log {
>>> compress
>>> dateext
>>> maxage 365
>>> rotate 99
>>> size=+1024k
>>> notifempty
>>> missingok
>>> create 644 policyd policyd
>>> }
>>
>> copytruncate or a restart of cluebringer is missing iirc.
>>
>> I use copytruncate, so I do not need to restart cbpolicyd
>
> I never use it. Could you point out how I ve to use it?
Truncate the original log file in place after creating a copy, instead
of moving the old log file and optionally creating a new one, It can
be used when some program can not be told to close its logfile and thus
might continue writing (appending) to the previous log file forever.
Note that there is a very small time slice between copying the file and
truncating it, so some logging data might be lost. When this option
is used, the create option will have no effect, as the old log file
stays in place.
>
> Tnx,
>
> Rocsca
>
> BTW: what is the menings of "iirc"?
If I remember correctly
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
