On a raspbian GNU/Linux 8 system, I get these errors during bootup:
ifplugd(eth0): Executing '/etc/ifplugd/ifplugd.action eth0 up'. ifplugd(eth0): client: /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory ifplugd(eth0): client: run-parts: /etc/ifplugd/action.d//ifupdown exited with return code 1 ifplugd(eth0): Program execution failed, return value is 1.
Later on, ifplugd repeats the action and succeeds. I suspect the initial failure is due to /run not being mounted. My questions are:
Is this normal behaviour or a bug/misconfiguration? ifplugd runs while systemd-fsck is still running, so it seems ifplugd is a bit early? Can I just ignore this problem?
Mounting /run appears to be a special case not handled by /etc/fstab because it needs to be present very early. So which part controls the mounting of /run? Is this done by systemd? If so, which part of systemd?