Print

Print


On 08/20/2018 01:33 PM, Adrian Sevcenco wrote:
> Hi! I see no explicit mention about the interaction of -s argument and
> all.pidpath setting .. i seen that my removing the all.pidpath it seems to not have
> any effect but i would like to make sure :
i spoke too soon : a duplicate of pid files are created in /tmp/<instance name>/
and even more they have different format :

aliprod@storage03: ~ $ cat /tmp/server/xrootd.pid ;echo
2983

aliprod@storage03: ~ $ cat /tmp/server/cmsd.pid ; echo
2956
&pfx=/storage01/xrdnamespace
&ap=/home/aliprod/alicexrdrun/admin/server/.olb/
&cn=3122rd.spacescience.ro

so ... i would think this is a bug from two view points :
pid files should contain only the pid ( in this case cmsd.pid have a problem)
and also  -s option should overwrite all.pidpath

What do you think? Should i add an issue on github?
Thanks a lot!
Adrian


> Can i safely remove all.pidpath setting if i specify the pid file with -s ?
> 
> Also, as a request, given that all.adminpath is also a service steering option
> can an option be added to xrootd|cmsd executables?
> 
> Thank you!
> Adrian
> 
> ########################################################################
> Use REPLY-ALL to reply to list
> 
> To unsubscribe from the XROOTD-L list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1



########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1