Change to /var/run and /var/lock

Scott James Remnant scott at
Wed Jan 11 09:12:13 GMT 2006

As has been discussed frequently over the past few weeks, I've now
changed /var/run and /var/lock to be both tmpfs filesystems.

Files, sockets, etc. in both should already be expected to be lost at
reboot, otherwise you were using the wrong directory.  Applications may
need to be modified if they expect a sub-directory to exist underneath
them, but at least for most things in main, this has already happened.

This change was made because with the increasing number of services
being started by udev (most notably networking), there needed to be a
writable place to store pid files and state for them.  Rather than
invent yet another path for them, we elected to use the two paths
intended for this purpose anyway.

Note that if you have /var on a separate filesystem, this should still
be fine.  The mountall script will move /var/run and /var/lock out of
the way while it mounts that, and put them back afterwards.

Of course, on the positive side, if you have state files that should be
thrown away at each reboot; rather than cleaning them up at boot or
start time, just put them in /var/run instead.

*wonders if a few /etc files can move to /var/run now*

Scott James Remnant
scott at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :

More information about the ubuntu-devel-announce mailing list