[pulseaudio-discuss] system-wide daemon

[Maarten Bosmans]

2010/2/11 Lennart Poettering <lennart at poettering.net>:
> On Wed, 10.02.10 10:45, Maarten Bosmans (mkbosmans at gmail.com) wrote:
>
>> The other mode is the system-wide daemon mode. This follows more the
>> traditional unix model of a dedicated pulse user running a daemon to
>> which other users can connect. The system mode is more applicable to
>> an audio server/appliance scenario.
>
> I would actually argue that the normal per-session PA logic is much
> more unixish than anything else. At least on my classic TTYs the bell
> sound was actually generated in the terminal computer and not on the
> server computer. And on the old standalone X terminals, it's the very
> same thing. XBell() is called on the terminal server, and the X terminal
> generates the sound.

That makes sense for the bell.

I was referring to the daemon though. In my view the system wide
daemon running as a dedicated user (apache, postgres) is an example of
the traditional unix model and the per-user daemon (dbus, pulse) is
another approach that is gaining a lot of popularity lately on linux
distributions.

Maarten

> So, what was true for teletype and X terminals back in the 80s, where
> the beep sound was played by an app on the terminal server and
> generated on the terminal client, is still true in the PA world: the
> audio stream a music player app plays on the terminal server is played
> back on the terminal client.
>
> So, once and for all, if someone complains that PA wasn't unixish
> enough: first of all, I don't care, and secondly that's a completely
> bogus statement and is not true.
>
> Lennart
>
> --
> Lennart Poettering                        Red Hat, Inc.
> lennart [at] poettering [dot] net
> http://0pointer.net/lennart/           GnuPG 0x1A015CC4
> _______________________________________________
> pulseaudio-discuss mailing list
> pulseaudio-discuss at mail.0pointer.de
> https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
>