From jon at radscan.com  Sat Sep 11 14:22:13 2004
From: jon at radscan.com (Jon Trulson)
Date: Sat, 11 Sep 2004 14:22:13 -0600 (MDT)
Subject: [nas] NAS 1.6e (devel) is now available.
Message-ID: <Pine.LNX.4.61.0409111420450.21796@m5.radscan.com>


 	.. at the usual place.

 	Some minor fixes for an impending 1.7 release.

            - clear CFLAGS before building config/config.h

            - emit the release string to the log and stdout when
              verbose is enabled.

            - if '-V' specified, emit release string and stdout and exit.

            - add a limit of 5 retries on failure to open input device.

            - barring major problems, this is a release candidate.


-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
"I am Nomad." -Nomad



From pengland at cmtkg.com  Sun Sep 12 19:29:28 2004
From: pengland at cmtkg.com (Paul England)
Date: Mon, 13 Sep 2004 10:29:28 +0900
Subject: [nas] No love (could not create audio connection block info when starting)
In-Reply-To: <4144F76B.9080403@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com>
Message-ID: <4144F7F8.4060707@cmtkg.com>

I get the following error

Fatal server error:
could not create audio connection block info

when running:
nasd :x -aa &

where x = 1 thru 65000 or so (I wrote a script to try them all).
This is strange, as I know not all network ports are in use.
Any help is appreciated

Regards
Paul



From jon at radscan.com  Sun Sep 12 23:25:51 2004
From: jon at radscan.com (Jon Trulson)
Date: Sun, 12 Sep 2004 23:25:51 -0600 (MDT)
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <4144F7F8.4060707@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com>
Message-ID: <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com>

On Mon, 13 Sep 2004, Paul England wrote:

> I get the following error
>
> Fatal server error:
> could not create audio connection block info
>
> when running:
> nasd :x -aa &
>
> where x = 1 thru 65000 or so (I wrote a script to try them all).
> This is strange, as I know not all network ports are in use.
> Any help is appreciated
>

 	What version of nas are you running?  If you are using a newer 
version (1.6d or better) try running nas with '-v -d 99' and see if you 
get better information (maybe in your syslog file).

 	This error usually means that it could not access the audio 
hardware for some reason...

-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
"I am Nomad." -Nomad



From pengland at cmtkg.com  Mon Sep 13 01:18:04 2004
From: pengland at cmtkg.com (Paul England)
Date: Mon, 13 Sep 2004 16:18:04 +0900
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com> <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com>
Message-ID: <414549AC.9040107@cmtkg.com>

Thanks for the reply Jon.
I dug around a bit, and I think I've fixed it (won't know until the morning)

I had to shutdown the machine in a rather nasty way today.  I think this 
was
the root of the problem.  I looked in /tmp/.sockets, and saw that audio0 
through
audio5000+ was taken (probably what happened when I ran my perl script
to find an open port) :(.

Anyways, I deleted all of these and restarted.  I'm thinking I've got 
the problem
fixed.  nasd starts, and my Qt app thinks that NASD is available, so 
that's definitely
better than before.

I'll come back wining in the morning if it doesn't though.

Regards
Paul

> On Mon, 13 Sep 2004, Paul England wrote:
>
>> I get the following error
>>
>> Fatal server error:
>> could not create audio connection block info
>>
>> when running:
>> nasd :x -aa &
>>
>> where x = 1 thru 65000 or so (I wrote a script to try them all).
>> This is strange, as I know not all network ports are in use.
>> Any help is appreciated
>>
>
>     What version of nas are you running?  If you are using a newer 
> version (1.6d or better) try running nas with '-v -d 99' and see if 
> you get better information (maybe in your syslog file).
>
>     This error usually means that it could not access the audio 
> hardware for some reason...
>



From drichard at largo.com  Mon Sep 13 14:33:27 2004
From: drichard at largo.com (David Richards)
Date: Mon, 13 Sep 2004 16:33:27 -0400
Subject: [nas] AudioOSS with Xine
Message-ID: <1095107607.11722.99.camel@test.largo.com>

All-

   Just wanted to pass along that because of increasing need for video
playback, we have been testing NAS and AudioOSS with XINE on our NCD
thin clients and it's working really well.  Not bad for thin clients
built in 1998!  Quicktime, Windows Media, RealPlayer, Audio CD and
streaming video/audio stations are all working.

   Next up is connecting Xine to V4L and running centralized floating TV
tuners to thin clients :P

Thanks to everyone that has developed and continues to develop NAS.

Dave Richards 
City of Largo, Florida.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://radscan.com/pipermail/nas/attachments/20040913/1a6d0332/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smiley-10.png
Type: image/png
Size: 848 bytes
Desc: not available
URL: <http://radscan.com/pipermail/nas/attachments/20040913/1a6d0332/attachment.png>

From pengland at cmtkg.com  Mon Sep 13 18:11:00 2004
From: pengland at cmtkg.com (Paul England)
Date: Tue, 14 Sep 2004 09:11:00 +0900
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <414549AC.9040107@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com> <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com>
Message-ID: <41463714.4040607@cmtkg.com>

Yeah, this is a bad problem.
I'm running on RH8, and ARTS does not start when the system comes up.
nasd runs (on the default port), and my QT app connects to it okay.
There's a function that should either return okay when sound is available
through nasd, or an error, when not available.  It never returns the error,
and the program plays the sound.  However.... no sound. :(

Yeah, I checked the speakers and all that jazz as well.

The following are the only errors I see in the syslog, but even that 
shouldn't
mean that sound is unavailable...  most other machines on my network have
this error, but play sound.

Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module sound-slot-1
Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
sound-service-1-0
Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module sound-slot-1
Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
sound-service-1-0

Any insight is appreciated.
Regards
Paul

> Thanks for the reply Jon.
> I dug around a bit, and I think I've fixed it (won't know until the 
> morning)
>
> I had to shutdown the machine in a rather nasty way today.  I think 
> this was
> the root of the problem.  I looked in /tmp/.sockets, and saw that 
> audio0 through
> audio5000+ was taken (probably what happened when I ran my perl script
> to find an open port) :(.
>
> Anyways, I deleted all of these and restarted.  I'm thinking I've got 
> the problem
> fixed.  nasd starts, and my Qt app thinks that NASD is available, so 
> that's definitely
> better than before.
>
> I'll come back wining in the morning if it doesn't though.
>
> Regards
> Paul
>
>> On Mon, 13 Sep 2004, Paul England wrote:
>>
>>> I get the following error
>>>
>>> Fatal server error:
>>> could not create audio connection block info
>>>
>>> when running:
>>> nasd :x -aa &
>>>
>>> where x = 1 thru 65000 or so (I wrote a script to try them all).
>>> This is strange, as I know not all network ports are in use.
>>> Any help is appreciated
>>>
>>
>>     What version of nas are you running?  If you are using a newer 
>> version (1.6d or better) try running nas with '-v -d 99' and see if 
>> you get better information (maybe in your syslog file).
>>
>>     This error usually means that it could not access the audio 
>> hardware for some reason...
>>
>



From pengland at cmtkg.com  Tue Sep 14 01:41:18 2004
From: pengland at cmtkg.com (Paul England)
Date: Tue, 14 Sep 2004 16:41:18 +0900
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <41463714.4040607@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com> <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com> <41463714.4040607@cmtkg.com>
Message-ID: <4146A09E.30905@cmtkg.com>

This has gone beyond crappy.
I've tried a host of differen things. I got my application top lay sound 
ONE time.
After that, I logged out, logged in as the user would, and once again -- 
no sound.
So basically, I've had sporadic at best results, following intuition and 
advice.

Every now and again I can get nasd to start, but it either doesn't play 
sound,
or complaints that /dev/dsp is busy.  I use Redhats cheesy little 
"detect sound
device" applet, and it always detects the device, and is able to play 
the sound,
even when NASD thinks it's busy.

The only thing consistent is when I run arts :x -aa,
/tmp/.sockets/audiox will be created, meaning I can't use that port anymore.

I'm starting the system with ARTS off, by the way.

Thanks
Paul

> Yeah, this is a bad problem.
> I'm running on RH8, and ARTS does not start when the system comes up.
> nasd runs (on the default port), and my QT app connects to it okay.
> There's a function that should either return okay when sound is available
> through nasd, or an error, when not available.  It never returns the 
> error,
> and the program plays the sound.  However.... no sound. :(
>
> Yeah, I checked the speakers and all that jazz as well.
>
> The following are the only errors I see in the syslog, but even that 
> shouldn't
> mean that sound is unavailable...  most other machines on my network have
> this error, but play sound.
>
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-slot-1
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-service-1-0
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-slot-1
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-service-1-0
>
> Any insight is appreciated.
> Regards
> Paul
>
>> Thanks for the reply Jon.
>> I dug around a bit, and I think I've fixed it (won't know until the 
>> morning)
>>
>> I had to shutdown the machine in a rather nasty way today.  I think 
>> this was
>> the root of the problem.  I looked in /tmp/.sockets, and saw that 
>> audio0 through
>> audio5000+ was taken (probably what happened when I ran my perl script
>> to find an open port) :(.
>>
>> Anyways, I deleted all of these and restarted.  I'm thinking I've got 
>> the problem
>> fixed.  nasd starts, and my Qt app thinks that NASD is available, so 
>> that's definitely
>> better than before.
>>
>> I'll come back wining in the morning if it doesn't though.
>>
>> Regards
>> Paul
>>
>>> On Mon, 13 Sep 2004, Paul England wrote:
>>>
>>>> I get the following error
>>>>
>>>> Fatal server error:
>>>> could not create audio connection block info
>>>>
>>>> when running:
>>>> nasd :x -aa &
>>>>
>>>> where x = 1 thru 65000 or so (I wrote a script to try them all).
>>>> This is strange, as I know not all network ports are in use.
>>>> Any help is appreciated
>>>>
>>>
>>>     What version of nas are you running?  If you are using a newer 
>>> version (1.6d or better) try running nas with '-v -d 99' and see if 
>>> you get better information (maybe in your syslog file).
>>>
>>>     This error usually means that it could not access the audio 
>>> hardware for some reason...
>>>
>>
>



From jon at radscan.com  Tue Sep 14 17:42:55 2004
From: jon at radscan.com (Jon Trulson)
Date: Tue, 14 Sep 2004 17:42:55 -0600 (MDT)
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <41463714.4040607@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com>
 <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com>
 <41463714.4040607@cmtkg.com>
Message-ID: <Pine.LNX.4.61.0409141738330.11904@m5.radscan.com>

On Tue, 14 Sep 2004, Paul England wrote:

> Yeah, this is a bad problem.
> I'm running on RH8, and ARTS does not start when the system comes up.
> nasd runs (on the default port), and my QT app connects to it okay.
> There's a function that should either return okay when sound is available
> through nasd, or an error, when not available.  It never returns the error,
> and the program plays the sound.  However.... no sound. :(

 	One of the issues I ran into with ALSA sometime ago is that when 
it starts, it mutes all the outputs.  I assume you did check for that? 
Also, what happens if you just cat a .wav file to /dev/dsp ?

>
> Yeah, I checked the speakers and all that jazz as well.
>
> The following are the only errors I see in the syslog, but even that 
> shouldn't
> mean that sound is unavailable...  most other machines on my network have
> this error, but play sound.
>
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module sound-slot-1
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-service-1-0
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module sound-slot-1
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-service-1-0
>

 	I see these too (on Mandrake 7.1), no idea what those really mean, 
but everything does still work...  I always used to use OSS, but I wanted 
to try out midi, and the apps I wanted to use required the ALSA MIDI 
interface, so I installed it, enabling the OSS emulation.  I haven't had 
any problems with it.  I'm using an SB 128 PCI.



> Any insight is appreciated.
> Regards
> Paul
>
>> Thanks for the reply Jon.
>> I dug around a bit, and I think I've fixed it (won't know until the 
>> morning)
>> 
>> I had to shutdown the machine in a rather nasty way today.  I think this 
>> was
>> the root of the problem.  I looked in /tmp/.sockets, and saw that audio0 
>> through
>> audio5000+ was taken (probably what happened when I ran my perl script
>> to find an open port) :(.
>> 
>> Anyways, I deleted all of these and restarted.  I'm thinking I've got the 
>> problem
>> fixed.  nasd starts, and my Qt app thinks that NASD is available, so that's 
>> definitely
>> better than before.
>> 
>> I'll come back wining in the morning if it doesn't though.
>> 
>> Regards
>> Paul
>> 
>>> On Mon, 13 Sep 2004, Paul England wrote:
>>> 
>>>> I get the following error
>>>> 
>>>> Fatal server error:
>>>> could not create audio connection block info
>>>> 
>>>> when running:
>>>> nasd :x -aa &
>>>> 
>>>> where x = 1 thru 65000 or so (I wrote a script to try them all).
>>>> This is strange, as I know not all network ports are in use.
>>>> Any help is appreciated
>>>> 
>>> 
>>>     What version of nas are you running?  If you are using a newer version 
>>> (1.6d or better) try running nas with '-v -d 99' and see if you get better 
>>> information (maybe in your syslog file).
>>> 
>>>     This error usually means that it could not access the audio hardware 
>>> for some reason...
>>> 
>> 
>

-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
"I am Nomad." -Nomad



From jon at radscan.com  Tue Sep 14 17:58:25 2004
From: jon at radscan.com (Jon Trulson)
Date: Tue, 14 Sep 2004 17:58:25 -0600 (MDT)
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <4146A09E.30905@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com>
 <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com>
 <41463714.4040607@cmtkg.com> <4146A09E.30905@cmtkg.com>
Message-ID: <Pine.LNX.4.61.0409141743000.11904@m5.radscan.com>

On Tue, 14 Sep 2004, Paul England wrote:

> This has gone beyond crappy.

 	Sorry :(

> I've tried a host of differen things. I got my application top lay sound ONE 
> time.
> After that, I logged out, logged in as the user would, and once again -- no 
> sound.

 	Wonder if PAM is playing with the perms on the audio devices?


> So basically, I've had sporadic at best results, following intuition and 
> advice.
>
> Every now and again I can get nasd to start, but it either doesn't play 
> sound,
> or complaints that /dev/dsp is busy.

 	Only one app can be accessing the audio device at a time.  nasd, 
when running, and in it's default configuration, will always release the 
device when a flow is completed.  This way it does not hog 
the device.

 	Unfortunately esound, arts, etc do not.  They expect to own the 
device the entire time they are running.

 	You might try something like 'fuser -v /dev/dsp' next time that 
happens to see what process is holding the device open...

> I use Redhats cheesy little "detect 
> sound
> device" applet, and it always detects the device, and is able to play the 
> sound,
> even when NASD thinks it's busy.

 	Is the rh applet merely sending it's audio to 
esound/artsd/whatever rather than to the device directly?  If so, and one 
of those is the culprit holding the device open, then yes, that would work 
would it not? :)

 	try running strace on nasd when this happens.. something like:

 	strace -o/tmp/out nasd -aa -v -d 99

 	Then see if anything interesting is in /tmp/out.

>
> The only thing consistent is when I run arts :x -aa,
                                           ^^^^

 	nasd you mean?

> /tmp/.sockets/audiox will be created, meaning I can't use that port anymore.

 	Why?  as long as another process (ie: another nasd) isn't bound to 
that socket, the new nasd will just re-use it...  Otherwise, if it is 
bound to someone else, you will get something like an 'address already in 
use' error.

 	BTW... What version of NAS are you running?
[...]


-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
"I am Nomad." -Nomad



From nick at ing-simmons.net  Wed Sep 15 06:21:05 2004
From: nick at ing-simmons.net (Nick Ing-Simmons)
Date: Wed, 15 Sep 2004 13:21:05 +0100
Subject: [nas] No love (could not create audio connection block infowhen starting)
In-Reply-To: <Pine.LNX.4.61.0409141743000.11904@m5.radscan.com> from Jon
 Trulson on Tue, 14 Sep 2004 17:58:25 -0600 (MDT)
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com><Pine.LNX.4.61.0409122324200.3147@m5.radscan.com><414549AC.9040107@cmtkg.com> <41463714.4040607@cmtkg.com><4146A09E.30905@cmtkg.com><Pine.LNX.4.61.0409141743000.11904@m5.radscan.com>
Message-ID: <20040915122105.4658.1@llama.elixent.com>

Jon Trulson <jon at radscan.com> writes:
>> So basically, I've had sporadic at best results, following intuition and 
>> advice.
>>
>> Every now and again I can get nasd to start, but it either doesn't play 
>> sound,
>> or complaints that /dev/dsp is busy.
>
> 	Only one app can be accessing the audio device at a time.  

This seems not to be true with ALSA and OSS emulation.
OSS opens a "plug" device and that gets mixed with other sources.
(At least on my hardware.)

That said on SuSE8.3/SuSE9.0 the ALSA OSS emulation seemed fragile,
but seems ok on SuSE9.1 (2.6 kernal and ALSA 1.x) 


>nasd, 
>when running, and in it's default configuration, will always release the 
>device when a flow is completed.  This way it does not hog 
>the device.
>
> 	Unfortunately esound, arts, etc do not.  They expect to own the 
>device the entire time they are running.
>
> 	You might try something like 'fuser -v /dev/dsp' next time that 
>happens to see what process is holding the device open...
>
>> I use Redhats cheesy little "detect 
>> sound
>> device" applet, and it always detects the device, and is able to play the 
>> sound,
>> even when NASD thinks it's busy.
>
> 	Is the rh applet merely sending it's audio to 
>esound/artsd/whatever rather than to the device directly?  If so, and one 
>of those is the culprit holding the device open, then yes, that would work 
>would it not? :)
>
> 	try running strace on nasd when this happens.. something like:
>
> 	strace -o/tmp/out nasd -aa -v -d 99
>
> 	Then see if anything interesting is in /tmp/out.
>
>>
>> The only thing consistent is when I run arts :x -aa,
>                                           ^^^^
>
> 	nasd you mean?
>
>> /tmp/.sockets/audiox will be created, meaning I can't use that port anymore.
>
> 	Why?  as long as another process (ie: another nasd) isn't bound to 
>that socket, the new nasd will just re-use it...  Otherwise, if it is 
>bound to someone else, you will get something like an 'address already in 
>use' error.
>
> 	BTW... What version of NAS are you running?
>[...]




From jorgen.moquist at era-a.ericsson.se  Wed Sep 15 10:29:10 2004
From: jorgen.moquist at era-a.ericsson.se (=?ISO-8859-1?Q?Moquist_J=F6rgen?=)
Date: Wed, 15 Sep 2004 18:29:10 +0200
Subject: [nas] synray server 3.0 beta and nas-1.6d
Message-ID: <41486DD6.3060806@era-a.ericsson.se>

Hi i had success with nas-1.6d and solaris9/sunrayserver3.0
audioplay works fine now, not hanging after ~10k an audiofile.
as it was with sunrayserver2.0. /J?rgen


From pengland at cmtkg.com  Wed Sep 15 17:00:23 2004
From: pengland at cmtkg.com (Paul England)
Date: Thu, 16 Sep 2004 08:00:23 +0900
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <Pine.LNX.4.61.0409141743000.11904@m5.radscan.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com> <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com> <41463714.4040607@cmtkg.com> <4146A09E.30905@cmtkg.com> <Pine.LNX.4.61.0409141743000.11904@m5.radscan.com>
Message-ID: <4148C987.3030908@cmtkg.com>

I'm not sure, but it has played the sound when Arts was off.  Anyways, 
I've not gotten a chance ot play with this since then, as the user has 
been hogging his computer. :)   I could've sworn I disabled Arts before 
my last attempt, but sure enough, it was running after checking a few 
things.  I might get a stab at it before the week is out.

Thanks for everyone's help thus far

Paul

>     Is the rh applet merely sending it's audio to 
> esound/artsd/whatever rather than to the device directly?  If so, and 
> one of those is the culprit holding the device open, then yes, that 
> would work would it not? :)
>
>     try running strace on nasd when this happens.. something like:
>
>     strace -o/tmp/out nasd -aa -v -d 99
>
>     Then see if anything interesting is in /tmp/out.
>
>>
>> The only thing consistent is when I run arts :x -aa,
>
>                                           ^^^^
>
>     nasd you mean?
>
>> /tmp/.sockets/audiox will be created, meaning I can't use that port 
>> anymore.
>
>
>     Why?  as long as another process (ie: another nasd) isn't bound to 
> that socket, the new nasd will just re-use it...  Otherwise, if it is 
> bound to someone else, you will get something like an 'address already 
> in use' error.
>
>     BTW... What version of NAS are you running?
> [...]
>
>



From pengland at cmtkg.com  Wed Sep 15 17:59:43 2004
From: pengland at cmtkg.com (Paul England)
Date: Thu, 16 Sep 2004 08:59:43 +0900
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <4148C987.3030908@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com> <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com> <41463714.4040607@cmtkg.com> <4146A09E.30905@cmtkg.com> <Pine.LNX.4.61.0409141743000.11904@m5.radscan.com> <4148C987.3030908@cmtkg.com>
Message-ID: <4148D76F.60203@cmtkg.com>

Okay, I did get a  shot at this this morning.
Arts is definitely not running, but I still get "device busy".  I think 
the key is finding out what's hogging the device.

> I'm not sure, but it has played the sound when Arts was off.  Anyways, 
> I've not gotten a chance ot play with this since then, as the user has 
> been hogging his computer. :)   I could've sworn I disabled Arts 
> before my last attempt, but sure enough, it was running after checking 
> a few things.  I might get a stab at it before the week is out.
>
> Thanks for everyone's help thus far
>
> Paul
>
>>     Is the rh applet merely sending it's audio to 
>> esound/artsd/whatever rather than to the device directly?  If so, and 
>> one of those is the culprit holding the device open, then yes, that 
>> would work would it not? :)
>>
>>     try running strace on nasd when this happens.. something like:
>>
>>     strace -o/tmp/out nasd -aa -v -d 99
>>
>>     Then see if anything interesting is in /tmp/out.
>>
>>>
>>> The only thing consistent is when I run arts :x -aa,
>>
>>
>>                                           ^^^^
>>
>>     nasd you mean?
>>
>>> /tmp/.sockets/audiox will be created, meaning I can't use that port 
>>> anymore.
>>
>>
>>
>>     Why?  as long as another process (ie: another nasd) isn't bound 
>> to that socket, the new nasd will just re-use it...  Otherwise, if it 
>> is bound to someone else, you will get something like an 'address 
>> already in use' error.
>>
>>     BTW... What version of NAS are you running?
>> [...]
>>
>>
>



From pengland at cmtkg.com  Wed Sep 15 18:07:09 2004
From: pengland at cmtkg.com (Paul England)
Date: Thu, 16 Sep 2004 09:07:09 +0900
Subject: [nas] No love (could not create audio connection block info when
 starting)
In-Reply-To: <4148D76F.60203@cmtkg.com>
References: <4144F76B.9080403@cmtkg.com> <4144F7F8.4060707@cmtkg.com> <Pine.LNX.4.61.0409122324200.3147@m5.radscan.com> <414549AC.9040107@cmtkg.com> <41463714.4040607@cmtkg.com> <4146A09E.30905@cmtkg.com> <Pine.LNX.4.61.0409141743000.11904@m5.radscan.com> <4148C987.3030908@cmtkg.com> <4148D76F.60203@cmtkg.com>
Message-ID: <4148D92D.2000407@cmtkg.com>

Last email today - I promise!

lsof is the command I was looking for.  Shows that an internal 
application is using the
device.  I will beat that developer and then come back to the list.

(I actually got nasd to start once, but no sound came out, which was 
strange). 

> Okay, I did get a  shot at this this morning.
> Arts is definitely not running, but I still get "device busy".  I 
> think the key is finding out what's hogging the device.
>
>> I'm not sure, but it has played the sound when Arts was off.  
>> Anyways, I've not gotten a chance ot play with this since then, as 
>> the user has been hogging his computer. :)   I could've sworn I 
>> disabled Arts before my last attempt, but sure enough, it was running 
>> after checking a few things.  I might get a stab at it before the 
>> week is out.
>>
>> Thanks for everyone's help thus far
>>
>> Paul
>>
>>>     Is the rh applet merely sending it's audio to 
>>> esound/artsd/whatever rather than to the device directly?  If so, 
>>> and one of those is the culprit holding the device open, then yes, 
>>> that would work would it not? :)
>>>
>>>     try running strace on nasd when this happens.. something like:
>>>
>>>     strace -o/tmp/out nasd -aa -v -d 99
>>>
>>>     Then see if anything interesting is in /tmp/out.
>>>
>>>>
>>>> The only thing consistent is when I run arts :x -aa,
>>>
>>>
>>>
>>>                                           ^^^^
>>>
>>>     nasd you mean?
>>>
>>>> /tmp/.sockets/audiox will be created, meaning I can't use that port 
>>>> anymore.
>>>
>>>
>>>
>>>
>>>     Why?  as long as another process (ie: another nasd) isn't bound 
>>> to that socket, the new nasd will just re-use it...  Otherwise, if 
>>> it is bound to someone else, you will get something like an 'address 
>>> already in use' error.
>>>
>>>     BTW... What version of NAS are you running?
>>> [...]
>>>
>>>
>>
>



