From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: [Fwd: Re: [pulseaudio-discuss] pulseaudio debug mode]
Date: Mon, 26 Jul 2010 10:26:58 +0100 [thread overview]
Message-ID: <i2jkcu$c2o$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=aGfUBy-cF_DoOJVz+XbSc+vUrcKjxtVR6NR=_@mail.gmail.com>
'Twas brillig, and Raymond Yau at 26/07/10 04:22 did gyre and gimble:
> But I have another question ,
>
> did update manager stop pulseaudio server when the update manager want to
> update pulseaudio package ?
>
> Actually I don't notice yum -y update stop the PA server if it updated
> pulseaudio package (install new pulseaudio and remove old pulseaudio
> package) and restart PA server on Fedora 10
PA is *not* restarted when a new version is installed and I suspect this
does not happen on Fedora either (but I could be wrong).
The reason is that PA is a per-user daemon, not a system service. If
three users were logged in, then each of their PA servers would need to
be killed and restarted but due to console-kit, only the active user
would get access to the devices which could cause enumeration issues etc.
It could maybe be handled better, but doing so would be rather complex.
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2010-07-26 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1280097015.29696.8.camel@localhost.localdomain>
2010-07-25 23:31 ` [Fwd: Re: [pulseaudio-discuss] pulseaudio debug mode] Raymond Yau
2010-07-26 1:30 ` Chris
2010-07-26 1:45 ` Raymond Yau
2010-07-26 3:06 ` Chris
2010-07-26 3:22 ` Raymond Yau
2010-07-26 9:26 ` Colin Guthrie [this message]
2010-07-26 13:20 ` Raymond Yau
2010-07-26 4:00 ` Raymond Yau
2010-07-26 4:21 ` Raymond Yau
2010-07-26 9:29 ` Colin Guthrie
2010-07-26 11:12 ` Raymond Yau
2010-07-26 11:22 ` Chris
2010-07-27 0:36 ` Raymond Yau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='i2jkcu$c2o$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.