Print

Print


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?

Brian


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bbockelm in #365: Hi,\r\n\r\nReviving this ticket because other folks are complaining about it.\r\n\r\nThe 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?\r\n\r\n* XRootD RPM packages default to `/var/run/xrootd`, yet the packaging does not create `/var/run/xrootd` using the OS's mechanisms (`tmpfiles.d`).\r\n* 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.\r\n\r\nBrian"}],"action":{"name":"View Issue","url":"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