Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/var/run/apel is not persistent under CentOS 7 #161

Open
dvandok opened this issue Apr 15, 2021 · 1 comment
Open

/var/run/apel is not persistent under CentOS 7 #161

dvandok opened this issue Apr 15, 2021 · 1 comment
Labels

Comments

@dvandok
Copy link

dvandok commented Apr 15, 2021

On CentOS 7 with systemd, /var/run is a symlink to /run mounted on tmpfs. It starts out empty on reboot, so it is up to the software to populate it as necessary.
The common setting for the PID file under /var/run/apel results in failure on startup of the service because the pid file cannot be created.
The common way to deal with this seems to be to create the missing directories on the fly.

The latest rpm release https://github.com/apel/ssm/tree/3.2.0-1 still 'owns' /var/run/apel.

@drebatto
Copy link

Yes, it would be nice to have a configuration file for systemd-tmpfiles, e.g. /usr/lib/tmpfiles.d/apel.conf, with a single line:

d /var/run/apel 755 root root -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants