 |
 |
There are two big problems with the default log rotate config file.
1) Since log rotate runs as root, when it rotates the file and creates a new log file, the new log file is owned by root. At this point xrootd cannot write to the new file. This causes information loss. Either logrotate should preserve ownership on the new log file or simply not create it ahead of time as xrootd will create it when notified to close and reopen the log file (i.e. add the no create option). This has been a big out-of-the-box problem at many sites.
2) The header line that tell whee log rotate should look for log files include two locations a) the default when no instance name is used, and b) the location where an instance name is used. Unfortunately, if one or the other does not exists then log rotate sends an error email to root which eventually gets to the sysadmin completely annoying them as one gets generated each day. While this is not a critical problem it is sufficiently annoying to require a fix. Perhaps by adding the missing option may solve this problem.
Andy & Wei on behalf of Ilija
—
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