 |
 |
well, there are two cases : * -b (user/by hand management) : one will for sure specify -s .. is specified, why create another pid file? is confusing (of course if -s is missing then do the default in /tmp (or in TMPDIR if set)) * -b *IS NOT USED*, that means that the service management is done a management framework like systemd. while systemd supports the management of services that do the forking (-b in our case) but it requires the specification of the exact path of pidfile within the service unit, the recommended way is to run the service in foreground as systemd will take care of all descriptors, lifetime of service, including the status of service (can do restart if service is dead, etc..).. so the creation of pidfiles is more than useless... in the end, the simple proposition is: do not create pidfile unless '-b' AND NOT '-s' -- 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/1357#issuecomment-742055972 ######################################################################## 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