FYI, upstream bug: 1172542

On 05/18/2015 01:38 AM, Bill Maidment wrote:
> glusterfs-3.6.0.29-2.el7.x86_64 and glusterfs-3.6.0.29-2.el6.x86_64 have the bad logwatch.d file dated 19th Sept 2014. The previous version 3.40.59 was OK.
>
> Cheers
> Bill
>
> -----Original message-----
>> From:Bill Maidment <[log in to unmask]>
>> Sent: Monday 18th May 2015 13:47
>> To: [log in to unmask]
>> Subject: RE: Logrotate not working properly on SL7 (solved)
>>
>> It appears that the /etc/logwatch.d/glusterfs file has some globals defined which override the previous global definitions.
>> I'm not sure why this has suddenly become an issue on March 26th (maybe some logwatch.d filenames were renamed?)
>>
>> Cheers
>> Bill
>>   
>> -----Original message-----
>>> From:Bill Maidment <[log in to unmask]>
>>> Sent: Sunday 17th May 2015 13:57
>>> To: [log in to unmask]
>>> Subject: RE: Logrotate not working properly on SL7
>>>
>>> Just found a SL6.6 machine that is also ignoring daily in /etc/logrotate.conf
>>>   
>>> -----Original message-----
>>>> From:Bill Maidment <[log in to unmask]>
>>>> Sent: Sunday 17th May 2015 13:35
>>>> To: [log in to unmask]
>>>> Subject: Logrotate not working properly on SL7
>>>>
>>>> Hi
>>>> After the yum updates on 26th March 2014 my logrotate reverted to weekly rotation instead of the daily rotation defined in /etc/logrotate.conf
>>>> There wasn't a yum update for logrotate, so some other update has caused the problem.
>>>> I'm using logrotate-3.8.6-4.el7-x86_64
>>>> Anyone else found this issue?
>>>>
>>>> Cheers
>>>> Bill
>>>>
>>>>
>>>
>>

-- 
Pat Riehecky
Scientific Linux developer

Fermi National Accelerator Laboratory
www.fnal.gov
www.scientificlinux.org