[HEADS-UP] Moving /var/run and /var/lock to tmpfs in Rawhide
Nathanael D. Noblet
nathanael at gnat.ca
Tue Nov 23 23:56:37 UTC 2010
On 11/23/2010 03:02 PM, Till Maas wrote:
> On Tue, Nov 23, 2010 at 09:48:30PM +0100, Lennart Poettering wrote:
>> I hereby want to let everybody know that in the next days I will turn
>> /var/run and /var/lock on tmpfs on Rawhide/F15. This is in accordance
>> with the following accepted F15 feature:
> The release notes section contains this:
> | /var/run and /var/lock are now mounted from tmpfs, and hence emptied on
> | reboot. Applications must ensure to recreate their own files/dirs on
> | startup, and cannot rely that doing this at package installtion will
> | suffice
> But this does not mention tmpfiles.d which you wrote can be used instead
> of creating files or dirs on startup.
>> c) YOU need to edit your .spec file and place a %ghost where
>> c) YOU need to test if you package still works, and if necessary file
>> AVC bugs, add an /etc/tmpfiles.d drop-in file to your program, or patch
>> it so that it is able to recreate these directories beneath /var/run on
>> its own.
> Imho there should be a packaging guideline to make it clear what needs
> to be done in which cases. E.g. when to %ghost files and when not.
I'm curious, one of my packages has /var/run/dspam in the specfile and
/var/lock/subsystem/dspam used in the initscript... I added a %ghost for
the second and now I'm wondering if I even need to.. Should I revert
that change? and just %ghost /var/run/dspam ?
More information about the devel