Print

Print


Hi! The usage of -s option is somehow inconsistent with existence of all.pidpath setting.
1. -s declaration should invalidate/override any pidpath option from the configuration file
(one also could argue that being a service steering option, there should be only the command line option)
2. pid files generated by the pidpath declaration (not by -s) are inconsistent with each other: the cmsd.pid from pidpath directory (or /tmp/<instance> if pidpath is not defined) have extra information beside the pid (so the contents is not consistent with xrootd.pid that have only the xrootd pid)

Thank you!
Adrian


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/802

########################################################################
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