Quote:
Originally Posted by xj25vm
I have noticed that sometime during the past year or so a bunch of startup scripts in Slackware have started to use /run instead of /var/run - but others still use /var/run. Is it all going to move to using /run at some point, or is there some other convention behind it? I am trying to make sense of what the system is, as I have a few customised rc.* scripts of my own, and I would like to keep them in sync with the conventions the rest of Slackware uses.
|
In the Slackware 15.0 and beyond,
/var/run is a symlink pointing to
/run , which is de default state tracker folder. Previously,
/var/run was a bind mounting of
/run, but this started in introducing some mysterious issues in Plasma5 and probably other applications, so Slackware ended with adopting the solution general used by other distributions - this symlink.
In other words,
/var/run is provided only as legacy compatibility.
I recommend you to use
/run to store the PID files in your scripts.
