Date: Sat, 24 Jan 2004 18:00:59 +0100 (CET) From: Cordula's Web <cpghost@cordula.ws> To: geert.hendrickx@ua.ac.be Cc: freebsd-questions@freebsd.org Subject: Re: /dev/dsp: Device busy Message-ID: <20040124170059.E4B0F40822@fw.farid-hajji.net> In-Reply-To: <200401241616.57830.geert.hendrickx@ua.ac.be> (message from Geert Hendrickx on Sat, 24 Jan 2004 16:16:57 %2B0100) References: <200401241454.56184.geert.hendrickx@ua.ac.be> <200401241616.57830.geert.hendrickx@ua.ac.be>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > /dev/dsp: Device busy > > esd is the culprit. > But esd is not running... I checked it with ps. I'm having the same problem with mpg123, which uses esd: $ ps ax|grep esd $ mpg123 somefile.mp3 /dev/dsp: Device busy audio: Device busy $ ps ax|grep esd 11041 ?? Ss 0:00.14 esd -terminate -nobeeps -as 2 -spawnfd 5 $ kill 11041 $ ps ax|grep esd $ mpg123 somefile.mp3 This happens every time. It's definitively esd that doesn't let go of /dev/dsp, and for some reason, can't accept connections on its unix socket /tmp/.esd/socket. It's perhaps related to permissions (who starts esd)? I dunno exactly. I'm using a brute-force work-around here: #!/bin/sh # playmp3.sh -- brute force mpg123 (Bug: /dev/dsp: Device busy) until (mpg123 "$1") do sleep 1; done Ugly, but better than nothing. -- Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040124170059.E4B0F40822>