No, I started sndiod as root. It switched to _sndiod then failed to open audio device I restricted access to. No bugs with sound system. Just limit /dev/audio* to wheel only was a bad idea. Now everything is fine.
21.11.2013, 11:50, "Alexandre Ratchov" <[email protected]>: > On Thu, Nov 21, 2013 at 06:01:58AM +0400, Alexander Pakhomov wrote: > >> Got it with gdb. >> I restricted access to /dev/audio* to wheel (tried to restrict anybody else >> to hear my laptop mic), >> this causes sndiod to fail after privdrop(). > > you could start a private sndiod process to get exclusive access to > the hardware. > > First ensure that no programs are using the audio hardware which is > exclusive (not even the system sndiod). > > Then start as a regular user: > > sndiod -aon <your other options> > > then, optionnaly, you could crank to -20 the sndiod process > priority with renice(2). > > -- Alexandre
