Am 10.09.2014 17:12, schrieb Niels Sijm: > Package: systemd > Version: 208-8 > Severity: normal > > To prevent my SSD from wearing out too quickly, I adjusted "/etc/fstab" to > mount "/var/run" as tmpfs. This has worked well for years without any trouble. > > Some time ago, my Jessie install suddenly failed to initialize, entering some > kind of rescue mode. Log files and dmesg output indicated that D-Bus was not > working properly. Switching back to sysvinit made my OS boot properly again, > except for D-Bus related software. > > After trying almost everything, it turns out mounting /var/run as tmpfs caused > D-Bus connections to fail with the following syslog message: > > Failed to get D-Bus connection: Failed to connect to socket > /run/systemd/private: No such file or directory > > This error is thrown by both "systemd-cgroups-agent" and > "systemd-update-utmp". > > Due to the complexity of both systemd/D-Bus and tmpfs-mounted system > directories, I am not sure if this is a bug. However, I am glad that I found > out eventually and happy that I can use D-Bus enabled software in Debian > Testing again :-)
/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. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers