Hi Jan,
That capability will come in release 4 and is now present in git head. The
documentation is already online.
http://xrootd.org/doc/dev4/xrd_config.htm#_Toc377223408
See the extended -k option. If you choose to use it you will need to
implement your own log rotation scheme.
Andy
On Thu, 30 Jan 2014, Jan wrote:
> Follow-up on https://savannah.cern.ch/bugs/?88357
>
> We are using logrotate with the "copytruncate" option, but have seen that copying over several GiB of logs can cause xrootd (the EOS namespace in our case) to become sluggish (apparently ongoing logging will get slowed down by the concurrent disk activity, we get a warning if a "stat /" takes longer than 10sec).
> Could you see whether a SIGHUP handler can be installed that closes and re-opens logfiles? This would allow external logfile rotation via "mv", i.e. without actual data to be copied. SIGHUP is just a suggestion, of course.
>
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/82
—
Reply to this email directly or view it on GitHub.
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
