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

[Niels Sijm]

On 09/10/2014 07:03 PM, Michael Biebl wrote:
> 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?

Confirmed:

niels at laptop:/var$ ls -l lock run
lrwxrwxrwx 1 root root 9 Sep 10 12:31 lock -> /run/lock
lrwxrwxrwx 1 root root 4 Sep 10 12:31 run -> /run