Bug#783321: systemd opens file in /var/run and not in /run

[Michael Biebl]

Am 26.04.2015 um 00:36 schrieb Michael Biebl:
> Am 26.04.2015 um 00:05 schrieb Dmitry Katsubo:
>>
>> Afterwards the process systemd opens a file in /var/run, thus not
>> allowing me to unmount /var:

>> systemd opens a file in /run, thus allowing the administrator to umount
>> and e.g. repair /var volume.

> According to codesearch [1], we have quite a few locations where
> "/var/run/dbus/system_bus_socket" is hard-coded.


After thinking about this some more, I'm actually not convinced this is
a bug at all. /var/run/dbus/system_bus_socket is by far not the only
ressource, which could be openend from /var.

In the end, I think it's rather questionable if it's a good idea to run
fsck on a system partition in single user mode.
And if you want to do so, you'll just need to shut down all services,
sockets and processes manually, e.g. by running "systemctl stop foo.socket".

If you want to run a forced fsck, there are much better facilities, like
passing fsck.mode=force on the kernel-command-line [1].

Given this, I'm not sure if it's worth the effort to move the dbus
socket around and I'm inclined to just close this bug report.

I'll leave the decision to Simon though.


Michael

[1] man 8 systemd-fsck
-- 
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/20150426/eddee2e1/attachment-0002.sig>