On Tue, 2014-09-16 at 16:32 +0200, David Henningsson wrote: > Removing the 20-second delay sounds like the right thing to do, but I > wonder if it will cause startup problems? E g, if PA autospawns, and > there are no systemd modules or anything else keeping it alive (e g > because the user does not run systemd), and it's waiting for a client to > connect? Waiting for a client to connect? If you think that PulseAudio would exit immediately after starting, fear not: it won't exit until at least one client has connected. However, in the scenario that you describe it probably isn't a good idea to exit immediately after the first client has left, because another client might appear quickly after that. I believe this is why the delay exists in the first place. I think we could set the delay to zero in module-systemd-login/module-console-kit, so the immediate exiting would only be used when we have a login manager. > > (Some nitpicking: we can have more than one PA instance per user, if the > > extra instances are started with a different XDG_RUNTIME_DIR.) > > Okay, is this something we actively support, and that we won't cause > troubles anywhere else? (I suspect loading the esd support module won't > work...) What do you mean by "actively support"? There will necessarily be caveats to running two daemons simultaneously, you can't use sound cards from two daemons at the same time... We certainly actively support running src/tests/test-daemon.sh while also having the normal user daemon running, for example. -- Tanu
