Sorry, better yet is fuser -v for verbose (and check out k for kill...)
$ fuser -v /dev/dsp
USER PID ACCESS COMMAND
/dev/dsp patrick 21592 f.... sox
> On Sat, 8 Feb 2003, mick wrote:
>
> > device /dev/dsp can't be opened (Resource temporarily unavailable)
This means that another program is blocking /dev/dsp.
Jeff's earlier post should help once you've found the program:
<quote who="mick">
> 1. you have the correct output plugin selected
> 2. no other program is blocking the sound card
> 3. your sound card is properly configured
>
> I can safely say 3 is not the issue. What are then other two messages
> indictive of?
<quote who="Jeff Waugh">
1 means that the XMMS output plugin may not be correct - you can choose OSS,
ALSA, esd, arts, etc. If you're running KDE, you probably want to choose
arts. This is probably true, especially if 2 is also true.
2 means that your sound card may not support mixing in hardware, which means
that only one program can write to it at once. That is probably the case
with your hardware. What you have to do in this instance is write to a sound
server, which mixes in software and sends the result to the hardware -> esd
and arts are the most common sound servers used to do this (esd in GNOME,
arts in KDE).
</quote>
On Sat, 8 Feb 2003, Patrick Lesslie claimed:
> You can find out what process numbers are using /dev/dsp with
>
> fuser /dev/dsp
>
> Then pick them out with, say
> ps ax | grep <process number>
>
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
