Yeah, we might be trending into over-analyzing here. Maybe we just wait until we hear complaints about the current rotation strategy not being flexible enough? Other than making sure the log-rotations are done automatically, is there functionality we're missing? Brian On May 12, 2011, at 5:32 PM, Andrew Hanushevsky wrote: > Sounds like a very sane suggestion to me. > > -----Original Message----- From: Yang, Wei > Sent: Thursday, May 12, 2011 2:20 PM > To: Andrew Hanushevsky > Cc: Lukasz Janyst ; Tanya Levshina ; Doug Benjamin ; Douglas Strain ; xrootd-dev > Subject: Re: XRootD tag and RPMs > > while logrotate is a nice tool, the build in -k is a even nicer and simpler way to do this. I think -k can reduce just one more task T3 has to do, while those who has a need to use logrotate can remove -k from /etc/sysconfig/xrootd. > > regards, > Wei Yang | [log in to unmask] | 650-926-3338(O) > > > On May 12, 2011, at 1:38 PM, Andrew Hanushevsky wrote: > >> Let me weigh in. I suppose you can use log rotate in Linux but I doubt most >> sites would need any more flexibility than what xrootd provides by its >> simple log rotate capability. Plus you would need to write a script to do >> the actual log rotation beyond something what xrootd does as the log is left >> open until midnight after which time is renamed with a time stamp and that >> is the log you need to rotate. Frankly, I don't see why we look for >> complicated solutions when a simple one will do for the majority of people. >> If a site needs a complicated log rotate then they could do it for >> themselves. A tier 3 site need not be saddled with default complexity. I >> know that the feeling is that logrotate is simple and not complex. But >> remember complexity is relative. >> >> Andy >> >> -----Original Message----- From: Lukasz Janyst >> Sent: Thursday, May 12, 2011 2:48 AM >> To: Tanya Levshina >> Cc: Doug Benjamin ; Douglas Strain ; xrootd-dev >> Subject: Re: XRootD tag and RPMs >> >> Hi Tanya, >> >> we will cut the second rc after we do some testing with this one. >> Your request raises a more general question of how we should handle >> the log rotation. Specifying it as a parameter for xrootd in the >> sysconfig file has an advantage of keeping all the settings together >> but I would argue that we should use the standard logrotator (man 8 >> logrotate) of Linux as it is far more flexible and is widely >> considered as "the" tool for this sort of job which is what most >> admins would probably expect. >> >> Let me know what you think. >> >> Cheers, >> Lukasz >> >> 2011/5/12 Tanya Levshina <[log in to unmask]>: >>> Hi Lukasz, >>> >>> Sorry, but I just have noticed that [-k NUM] option is still missing from >>> /etc/sysconfig/xrootd configuration. This option controls the number of >>> days the log files will be kept. >>> >>> Could you please add this and cut a new rc? >>> >>> Thanks a lot, >>> Tanya >>> ----- Original Message ----- >>> From: Lukasz Janyst <[log in to unmask]> >>> Date: Wednesday, May 11, 2011 11:58 am >>> Subject: XRootD tag and RPMs >>> To: xrootd-dev <[log in to unmask]>, Doug Benjamin >>> <[log in to unmask]>, Tanya Levshina <[log in to unmask]>, Douglas >>> Strain <[log in to unmask]> >>> >>>> Dear all, >>>> >>>> I have made a rc1 tag and built the RPMs which you can access here: >>>> http://xrootd.cern.ch/sw/releases/3.0.4-rc1/ >>>> >>>> Cheers, >>>> Lukasz >>> >>