 |
 |
Hi, Reviving this ticket because other folks are complaining about it. The XRootD packaging is obviously wrong. While, yes, it's technically possible to correct the out-of-the-box issues, I don't understand why these can't be fixed in the packaging? * XRootD RPM packages default to `/var/run/xrootd`, yet the packaging does not create `/var/run/xrootd` using the OS's mechanisms (`tmpfiles.d`). * XRootD is set to start in `/` and, on RHEL7, requires you to specify a named instance (`-n` option). Hence the attempt to create `//clustered`. Suggestion: set the startup directory to not-`/ in the packaging. Brian -- 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/365#issuecomment-290276028 ######################################################################## 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