 |
 |
For reference, I have settled on: `all.adminpath /run/xrootd` which seems to work fine with SELinux, since the directory is shipped with the RPMs (with correct SELinux contexts) and contains the PID files (used by the `systemd` units). That seems to work out of the box. Of course, Andy's point still holds — while I'm personally a fan of using `/run/xrootd`, since it matches [FHS](https://refspecs.linuxfoundation.org/fhs), I'm probably not the standard admin out there ;-). -- 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/1502#issuecomment-911356726 ######################################################################## 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