On Sun, Mar 5, 2017 at 9:01 PM, Michael Biebl <bi...@debian.org> wrote: > On Fri, 20 Jan 2017 11:38:54 -0300 Felipe Sateler <fsate...@debian.org> > wrote: >> Control: tags -1 - unreproducible moreinfo >> Control: reassign -1 systemd >> Control: affects -1 rtkit >> Control: retitle -1 Units with PrivateTmp fail when /var is a symlink >> Control: severity -1 normal >> >> On 12 January 2017 at 04:46, Bogdan Vatra <bogdan.va...@kdab.com> wrote: >> > Hi, >> > >> > I have an update, some time ago (~1year) I run out of space on my system >> > partition and I decide to move /var folder to another partition and >> > symlink it >> > back to / partition. Today I just moved back my var folder and rtkit daemon >> > started to work ... :) >> >> This is a bug in systemd. A related issue is >> https://github.com/systemd/systemd/issues/3867 , but that is >> supposedly fixed in 232. BogDan, do you have version 232 installed? It >> may be that the issue is not fully fixed yet. > > If /var is a relative symlink to say mnt/var, it seems to work fine. > If /var is an absolute symlink to /mnt/var, rtkit-daemon fails to start > (complaining about /var/run/dbus/system_bus_socket not being available). > Tested with 232-18. > > That all said, I'm not sure if supporting such a setup is actually worth it. > If you need to move /var to a separate location, ideally you make it a > separate mount point. If that is not possible, I would suggest you bind > mount the directory. This works fine. > > Felipe, do you think this is worth investigating and spending time on?
If this only affects PrivateTmp when /var is a symlink, I agree it is a corner case not worth spending much time on. My guess was that this would be a bug in a more common part of the code, and that it may affect other mount-related settings (RootDirectory=, WorkingDirectory=). I haven't been able to cause similar errors with those settings though. -- Saludos, Felipe Sateler
