Re: permissions

[richard <richard.bown@xxxxxxxxxxxxxxxx>]

Hamish Moffatt wrote:
> On Mon, Oct 30, 2006 at 11:56:00PM +0000, richard wrote:
>   
> > > Still, the error "Device or resource busy" means that something is using
> > > the device, not that you don't have permission to access it (which would
> > > just be "Permission denied.") As root you might try using lsof to find
> > > out which program is using it
> > >
> > > eg "lsof /dev/dsp
> > >  
> > >       
> > I let gmfsk fail and produce the error message then ran the following:-
> > [root@gb7tf Desktop]# lsof /dev/dsp
> > [root@gb7tf Desktop]# lsof|grep /dev/dsp
> >     
>
> Maybe something is using the underlying ALSA device which is blocking
> /dev/dsp. lsof | grep /dev/snd ?
>
>
> Hamish
>   
Its only the mixer app Hamish
mixer_app  6382 richard-g8jvm   17u      CHR      116,0                
7895 /dev/snd/controlC0

I've also tried recompiling gmfsk as me and not as root
-rwxr-xr-x 1 root root 1283122 Oct 31 09:06 gmfsk*
-rwxr-xr-x 1 root root 1453277 Oct 23 12:17 gpredict*
-rwxr-xr-x 1 root root  822682 Oct 20 14:46 xlog*

Added the line that Al suggested in rc.local
chmod 666 /dev/dsp /dev/audio /dev/mixer /dev/cdrom

no immediate effect, but worked after rebooting, so it looks like the 
permissions
are only read at startup on the above files, which is a bit strange as 
normally you can change file permissions
on the hoof and take immediate effect.
Must be some Mandriva security measure that been added in MDV2007.

Thanks for all the help

73 Richard


-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html