Print

Print

The issue originates from #365 which has been marked as resolved. However, it seems like the resolution of #365 doesn't provide a very optimal solution to RHEL7 nature of handling the service run files. I.e. while /var/run/xrootd is created after yum update|install xrootd, it is not re-created when host is rebooted.

We think this is a bug on the packaging level and requires better solution than currently sysadmin do: a) systemd override using WorkingDirectory=/var/spool/xrootd or b) setting all.pidpath /var/run/xrootd -> /var/spool/xrootd in the xrootd config.

There were couple of options discussed, most viable and permanent solution according to tmpfiles.d manpages suggest create the file /usr/lib/tmpfiles.d/xrootd.conf with content:

/var/run/xrootd 0755 xrootd xrootd

Thanks,
Marian

—
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":"DESCRIPTION","message":"PID file /var/run/xrootd not re-created after reboot in RHEL7 (#648)"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/648"}}}

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