Bug#761076: systemd: Fails to start when /var/run is mounted as tmpfs

Michael Biebl biebl at debian.org
Wed Sep 10 18:03:28 BST 2014


Am 10.09.2014 18:10, schrieb Niels Sijm:
> On Wed, Sep 10, 2014 at 5:42 PM, Michael Biebl <biebl at debian.org> wrote:

>> /var/run is a symlink to /run since wheezy.
>>
>> I suspect, by mounting a tmpfs on /var/run, you "overmounted" /run with
>> a new tmpfs, nuking all the state that was stored there.
>>
> 
> That makes sense, thank you.
> 
> It also explains why only systemd was affected.

Well, this also affects sysvinit, but is less critical for sysvinit.

That said, can you please configurm that /var/lock is a symlink to
/run/lock and /var/run is a symlink to /run?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140910/a407b97d/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list