Bug#878401: [systemd] Dependency on /tmp not correctly stated for some sound.target (or /tmp/pulse-* shows up underneath my /tmp mount)
antonio.e.russo at gmail.com
Fri Oct 13 13:58:07 BST 2017
On 10/13/17 07:30, Michael Biebl wrote:
> That seems like the wrong approach. sound.target does not have any
> dependencies on /tmp.
> If anything, it's pulseaudio which should ensure that /tmp is mounted.
I agree, wholeheartedly. But getting this directory out of /tmp has
been a bug for 7 years .
> I am confused though: Are you suggesteting that pulseaudio is started by
> pulseaudio.service is supposed to be a systemd user service so this
> doesn't really make sense.
I don't know why a pulse directory is being created, but its right after
sound.target and after sound devices start getting loaded by the kernel.
Maybe there's some weird udev hook I should look for? Everything in
that has the word "pulse" in it, only seems to have environment variables
being set in them.
I will say that on other machines I'm looking at, the pulse directory is
created much later on, relative to the beginning of the systemd log.
***This particular machine has to wait around a long time for udev to settle,
(for a zpool import to start and finish). Maybe there's some race that
just usually isn't a problem otherwise?***
> Is it possible that pulseaudio is started via other means which are not
> under systemd's control?
I sent you journalctl -b in a private email. If there's anywhere else you
can think of looking, I'm open to suggestions.
When I get a chance, I'll try to add a dependency on /tmp to
sound.target to see if that delays the creation of /tmp/pulse-* .
More information about the Pkg-systemd-maintainers