 |
 |
Hi! Is my intention of moving the script based usage of xrootd service to systemd but i would see some details that can be improved :
i believe that log specification should not be fenced as all other options are relative to the name of configuration file .. so
-l /var/log/xrootd/xrootd.log
should be :
-l =/var/log/xrootd-%i.log
for both xrootd and cmsd ; i omitted the directory as multiple services with different users can potentially be run on the server
moreover i would say that the configuration file name is too long so i would suggest to replace
-c /etc/xrootd/xrootd-%i.cfg
with
-c /etc/xrootd/%i.cfg
Of course, it remains the problem of adminpath, with the mix of resident and non-resident files, the multiple pid files (found also in ADMINPATH// even is -s options was used) , the extra text found in ADMINPATH//cmsd.pid, the core files location specified by symlinks in ADMINPATH//.xrd/=/core/ that point to $HOME/ (and this is potentially problematic for services started by root), impossibility to specify the adminpath with cli argument so lacking the control of location to write files into if adminpath specification is missing in configuration file .... but these are of course for some other time
Thank you!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
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