-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/27/2012 10:57 AM, David A. De Graaf wrote:
On Tue, Jun 26, 2012 at 08:24:05PM -0500, Mikkel L. Ellertson wrote:
> You may want to look into running PA as a system daemon instead of a
> user daemon.
I have done so, and it didn't work. Specifically, I put these
commands into /etc/rc.d/rc.local:
# Start the pulseaudio daemon
/usr/bin/pkill -9 pulseaudio
/usr/bin/pulseaudio --kill
sleep 1
echo "/usr/bin/pulseaudio -D --system --log-target=syslog"
/usr/bin/pulseaudio -D --system --log-target=syslog
/usr/bin/play /usr/share/sounds/KDE-Im-Phone-Ring.ogg
Upon rebooting, no sound was produced, but a pulseaudio daemon was
found running with the --system option. Neither I nor root could
produce
any sound. The 'play' command ran for a time commensurate
with its
usual running time, but no sound emanated from the speakers.
Neither 'pulseaudio --kill' nor 'pkill pulseaudio' were able to
stop the daemon, either as root or as dad. root running 'kill -9 <pid>'
did kill it. With it gone, I could once again generate sound, but root
could not.
Perhaps I misunderstand the correct way to start a "system daemon" of
pulseaudio. I did also edit /etc/group, adding root and dad to groups
audio, pulse, pulse-access just for good measure.
Reading 'man pulseaudio' tells me the --system option is not
recommended. Perhaps the consequences are so dire and
world-threatening that the developer has made it inoperative.
It tells us that a special configuration is needed, but provides no
clue what that may be.
You need to edit the files in /etc/pulse. You at lease need to
modify the daemon.conf file. You will probably want uncomment
daemonize and system-instance and change them to yes.
Mikkel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAk/rSgIACgkQqbQrVW3JyMR/oACdGu6Trd1d6F5ud0wIrAllZR6o
PZ4An08JqM2MNoWzchCOjU/kJ6TPNn7Z
=+3W3
-----END PGP SIGNATURE-----