Am Freitag, den 29.01.2010, 20:16 -0800 schrieb Vagrant Cascadian: […]
> when running pulseaudio from ltsp, it produces a lot of messages to syslog: > > Jan 29 19:08:02 ltsp20 pulseaudio[1733]: main.c: OK, so you are running PA > in sy > stem mode. Please note that you most likely shouldn't be doing that. > Jan 29 19:08:02 ltsp20 pulseaudio[1733]: main.c: If you do it nonetheless > then i > t's your own fault if things don't work as expected. > Jan 29 19:08:02 ltsp20 pulseaudio[1733]: main.c: Please read > http://pulseaudio.o > rg/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is > usually > a bad idea. Are those messages just printed once, every time a user connects or for another event? > so, i go to the URL mentioned, and it gives a reasonable explanation about why > it's bad. that's all good, but then it explains the valid use case: > > So why have it then? > > System mode is around for usage on thin client or embedded setups, wher no > real > local user exists, where access is exclusively via the network, and where > state > data is flushed on each session termination. > > so, i happen to be using it for a thin client system, LTSP... but there > appears > to be no way to quiet it if you're using --system in the mentioned valid use > case... i could set the log level, but then i might miss messages i actually > want about other issues. hrm. That looks like something which should be reported/discussed/fixed upstream. Could you please write a message to pulseaudio-discuss. Thanks, Paul [1] https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Pkg-pulseaudio-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-pulseaudio-devel
