On Mon, 2015-12-07 at 10:36 +0100, David Henningsson wrote: > Hi! > > Sorry for the late reply. > > When starting child processes, there is a helper function in > src/pulsecore/start-child.c that you can use. It should cover the > platform and security questions you're having. (Or at least put the ball > back into our ballpark. :-) ) > > That said, about the general concept of launching an executable on > suspend/resume...it seems useful to me, but should such an executable be > blocking or non-blocking (i e, resume/suspend continuing in parallel, or > waiting for the executable to finish)? > What do others think? It should be non-blocking. The original use case doesn't require blocking behaviour, and non-blocking is a safer default (lesser risk of causing audio drop-outs on other devices). -- Tanu
