What would likely cause directories in /var/run to disappear / not be created on startup? (CentOS 7.3)

{/var,}/run is vaporized by systemd on boot. It's a wonderful and entirely unexpected surprise with such low value.

If you want to ensure a directory exists after boot, you'll have to hook something in with the tmpfiles section of systemd.

/usr/lib/tmpfiles.d/httpd.conf
::::::::::::::
d /run/httpd   710 root apache
d /run/httpd/htcacheclean   700 apache apache

/usr/lib/tmpfiles.d/mariadb.conf
::::::::::::::
d /var/run/mariadb 0755 mysql mysql -

And, if your tmpfiles entries are missing, I'm betting you hand-roll your own packages (and tune, and test, and promote, for every.single.release). As long as we agree it's usually a bad idea for anything with scale or an SLA, that's cool though.

Tags:

Process

Startup

Centos

Var

Systemd

Related

rsync --no-perms still preserves permissions and ignores umask Debian laptop installation fails due to debootstrap error "Failed to determine the codename for the release" at "Install the base system" difference copy contents folder between /. and /* in linux Xfce panel config file is rewritten with old contents How can I remove the BOM from a UTF-8 file? $HOME/bin dir is not on the $PATH How to resume package building in debian? How do I shorten the current directory path shown on terminal? Headphones with combo jack: Force internal mic for input and headphones for output Why can't I create a `hardlink` to a file from a "mount --bind" directory on the same filesystem? uname is broken: how do I determine the currently running kernel? Editing text file with Vim does not update tail -f

Recent Posts