[systemd-devel] systemctl disable <service> not working as expected

Belal, Awais Awais_Belal at mentor.com
Mon Jun 1 07:49:11 PDT 2015

Hi Lennart

Thanks a lot for the reply. I believe it is off-topic here and I should rather post on the pulseaudio mailing list but please answer the below and I will come over to the pulse mailing list if need be.

I have autospawn = no and daemon-binary = /bin/true in my client.conf but I still see pulseaudio being triggered... :(
Can you please suggest a way on how I can disable it completely other than deleting/renaming the binary? Is the autospawn config not enough to make sure pulse is never started during system boot?


From: Lennart Poettering [lennart at poettering.net]
Sent: Friday, May 29, 2015 6:59 PM
To: Belal, Awais
Cc: systemd-devel at lists.freedesktop.org
Subject: Re: [systemd-devel] systemctl disable <service> not working as expected

On Fri, 29.05.15 11:19, Belal, Awais (Awais_Belal at mentor.com) wrote:

> Hi,
> I am working on an x86_64 platform with a yocto based environment. I
> was trying to disable pulseaudio which is included in the system by
> default so I did a 'systemctl disable pulseaudio' but when I reboot
> it seems pulseaudio is still run for a very short period of time and
> this is messing up some sound controls on my system. Although
> SYSVINIT capability is enabled but no sysv init style scripts are
> available on the target. Any pointers will be really helpful.

pulseaudio is generally not a system service but a user
service. Unless your user session is fully converted to be managed by
systemd too (which is unlikely) systemd is hence not involved at all
with starting it.

PA is usually started from the session setup script or service. In
Gnome that's gnome-session, for example. It's also auto-spawned
on-demand if the libraries are used and note that it is missing.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list