Joshua Murphy wrote: > Well, given that it's there, it cleans up after itself, and it avoids > issues in the instance where /var isn't available early on, is there > much reason _not_ to link /var/run and /var/lock over to their > respective equivalents on /run? And both with and without /var mounted > (so they exist and are writable even if /var doesn't come up)? If I > recall its purpose properly, /var exists to hold data that _needs_ to > be writable in an actively running system, logs, lock files, caches, > etc.. but as tmpfs didn't exist back when it was thought up, no > separation was explicitly defined between persistent and > non-persistent data. With /run around now, there's an explicitly > defined lack of persistence that would suit /var/run and /var/lock > rather well, since stale service pids, lock files, and the like can > wreak havoc on an unplanned restart (which tends to be bad enough with > the prospect of, say, a failed UPS as it is). Also, any > inconsistencies in the above rambling curiosity (as well as the > rambling itself, I should note) are the result of having been awake > far too early for a Saturday, and still being awake for the start of > Sunday, so apologies may be required on my part. >
Well, I don't see why not. As you say, lack of a proper clean up after a bad shutdown can cause problems. Anything in /run would disappear after a shutdown, clean or not, since it is in tmpfs. It doesn't seem to use much ram either. I really don't know of a reason why it couldn't be set that way. I'm not the sharpest tool in the shed tho. lol As for one of us setting it to do that manually, I guess one could do that. If I recall correctly, /var/lock is *supposed* to be cleaned up when booting but that was a good long while ago. This may be something the devs are already getting ready for. I get the feeling that they are taking what I call baby steps. I noticed a upgrade to baselayout and I think OpenRC as well not long ago. I'm not sure what decided to put stuff in /run. I would think it would be one of those but it could be some other package. I guess udev could be one that could have made it as well. It does have a directory in there that has stuff in it. The rest are empty. I'd wait for a serious guru to reply before changing anything tho, just to be safe. ;-) You think being up late at night is bad. You should see me when my meds are making me goofy. lol Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
