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

2015-05-08 Thread Dmitry Katsubo
On 2015-04-27 17:13, Simon McVittie wrote: On 26/04/15 13:12, Dmitry Katsubo wrote: Indeed other files could be opened from /var, but in single mode that is very limited. The only service that lock it is NFS mount (rpcbind). And I can always stop these services, thus allowing me to unmount

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

2015-04-27 Thread Simon McVittie
On 26/04/15 13:12, Dmitry Katsubo wrote: Indeed other files could be opened from /var, but in single mode that is very limited. The only service that lock it is NFS mount (rpcbind). And I can always stop these services, thus allowing me to unmount /var. But that is not the case with process

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

2015-04-26 Thread Marco d'Itri
On Apr 26, Michael Biebl bi...@debian.org wrote: The problem with /var/run/dbus/system_bus_socket is, that it's hard-coded in so many locations (as you can see on codesearch), one could even consider it ABI, that I'm worried that we might break quite a lot of stuff by changing it. I can't see

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

2015-04-26 Thread Michael Biebl
Hi Marco Am 26.04.2015 um 15:59 schrieb Marco d'Itri: On Apr 26, Michael Biebl bi...@debian.org wrote: The problem with /var/run/dbus/system_bus_socket is, that it's hard-coded in so many locations (as you can see on codesearch), one could even consider it ABI, that I'm worried that we

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

2015-04-26 Thread Marco d'Itri
On Apr 26, Michael Biebl bi...@debian.org wrote: My concern is, that /var/run might *not* be a symlink to /run. I am not sure, but then I would rather have these systems break in a more visible than subtle way. It's hard to quantify, how common that is. Probably not that much, but still.

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

2015-04-26 Thread Dmitry Katsubo
On 26/04/2015 01:05, Michael Biebl wrote: 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

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

2015-04-26 Thread Michael Biebl
Am 26.04.2015 um 14:12 schrieb Dmitry Katsubo: On 26/04/2015 01:05, Michael Biebl wrote: 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

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

2015-04-26 Thread Simon McVittie
On 25/04/15 23:36, Michael Biebl wrote: Simon, do you expect any breakage if we move the socket file to /run? /var/run should typically be a symlink to /var/run, so it should still be accessible under the old name. /var/run/dbus/system_bus_socket is the canonical interoperable path, hard-coded

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

2015-04-25 Thread Michael Biebl
Control: reassign -1 dbus Am 26.04.2015 um 00:05 schrieb Dmitry Katsubo: Package: systemd Version: 215-16 Hello, I run Debian jessie in single mode (recovery mode). In this mode I would like to start gpm service: # /etc/init.d/gpm start Afterwards the process systemd opens a file

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

2015-04-25 Thread Dmitry Katsubo
Package: systemd Version: 215-16 Hello, I run Debian jessie in single mode (recovery mode). In this mode I would like to start gpm service: # /etc/init.d/gpm start Afterwards the process systemd opens a file in /var/run, thus not allowing me to unmount /var: # lsof | grep /var systemd 1

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

2015-04-25 Thread 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.