On 07 Feb 2003 10:08:16 -0800 Fernando Pablo Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > Recently I've been having problems with the ownership/permissions of > > the/dev/<sound devices>. I'm not sure how and when it started > > happening. > > > > The devices take on the ownership of who logs on; eg if I log on, > > the devices are setup as, for example, > > > > crw-------- 1 dave audio 14, 3 ... /dev/dsp0 > > > > For me thats ok. > > > > If I subsequently logoff, and my son logs on, they change ownership > > to his logon. > > > > Where this is particularly a pain is when I logon as 'root' to start > > X & Gnome via gdm and logon that way, then the devices are set to > > > > crw-------- 1 root audio 14, 3 ... /dev/dsp0 > > > > ..and no sound comes out for anyone, 'cos no-ones got permission for > > the devices. > > > > However I manually change the permission setup (eg setting rw for > > the'audio' group, to which every logon is assigned), they always get > > reset to owner-only rw permission next boot-up. > > > > This is Alsa 0.9rc6 on Mandrake 9. > > I don't know if Mandrake uses the same directory structure for this as > RedHat, In Redhat /etc/security/console.perms defines how the > permissions get allocated for devices for console logins... (man > console.perms for more details - it is part of the pam package). > > -- Fernando > Mandrake does put console.perms in the same place as RH - and it was the culprit. Thanks. Still don't know why it changed though - it used to be okay and _I've_ never seen this file before.... a mystery... Dave ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
