Hi Lukasz,
I think the ownership get changed to root after rotation. I worked around this at SLAC by adding “ copytruncate” to /etc/logrotate.d/xrootd.
regards,
Wei Yang | [log in to unmask] | 1-650-926-3338
On Jul 25, 2014, at 6:43 AM, Lukasz Janyst <[log in to unmask]> wrote:
> Hi Wei,
>
> we don not use the "create" option in our logrotate script (see: man
> logrotate) so, if a logfile with wrong permissons is created, it's done
> by the xrootd daemon not logrotate.
>
> Cheers,
> Lukasz
>
> On 07/22/2014 11:40 PM, Yang, Wei wrote:
>> Thanks Andy. this is not about me:-)
>>
>> --
>> Wei Yang | [log in to unmask] | 650-926-3338(O)
>>
>>
>>
>>
>> On Jul 22, 2014, at 2:25 PM, Andrew Hanushevsky <[log in to unmask]> wrote:
>>
>>> Hi Wei,
>>>
>>> Two options: 1) change the logrotate options (I assume this is Linux), or 2)
>>> go back to the original internal log file rotation which works just fine.
>>>
>>> Andy
>>>
>>> -----Original Message-----
>>> From: Yang, Wei
>>> Sent: Tuesday, July 22, 2014 2:10 PM
>>> To: xrootd-dev
>>> Subject: logrotate for xrootd
>>>
>>> I installed 402 yesterday and there seems to be a problem with logrotate.
>>> after the rotation, the owner of /var/log/xrootd/xrootd.log belongs to
>>> root.root so no logging can be appended to this file.
>>>
>>> --
>>> Wei Yang | [log in to unmask] | 650-926-3338(O)
>>>
>>>
>>>
>>>
>>>
>>> ########################################################################
>>> Use REPLY-ALL to reply to list
>>>
>>> To unsubscribe from the XROOTD-DEV list, click the following link:
>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>>>
>>>
>>
>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
|