Greg Freemyer said the following on 12/27/2013 06:17 PM:
You should not be expecting anything in /run or /var/run to survive a reboot. Here's a LWN article about it:
An interesting article but I don't think it helps the OP.
Anyway in 13.1, /var/run is "tmpfs". Meaning there is no disk space backing it up. Thus on reboot, it gets recreated in it's virgin state every time.
Yes it gets recreated on boot and actually it does have disk space backing it up. This is an 'in memory' file system and like everything else 'in memory' it can, if needed, be paged out. Thus there *is* disk space backing it up: swap space.
As to how to change that, I'm not sure you can easily.
Yes you can, quite easily See TMPFILES.D(5)
If you data that needs to survive reboots, can't you just move it somewhere that is not a tmpfs?
That's a very good point. Any TMP might be volatile or get purged. Even files in systems where /tmp is a on-disk file system can get purged by routines stated by cron. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org