[nas] [maddog at mir.com: Bug#168814: some additional info...]

[Steve McIntyre]

And more information about the problem.

----- Forwarded message from Matto Marjanovic <maddog at mir.com> -----

From: Matto Marjanovic <maddog at mir.com>
Date: Wed, 13 Nov 2002 21:10:34 -0500
To: 168814 at bugs.debian.org
Reply-To: Matto Marjanovic <maddog at mir.com>, 168814 at bugs.debian.org
Subject: Bug#168814: some additional info...
X-Debian-PR-Message: report 168814
X-Debian-PR-Package: nas
X-Debian-PR-Keywords: 
X-Spam-Level: 
X-Spam-Status: No, hits=-8.9 required=5.0 tests=SENT_BY_BTS,IN_REP_TO,FORGED_RCVD_FOUND version=2.20
X-Spam-Level: 
X-Keywords:                 
X-UID: 149



Here are some more data points:

1) Setting "ReleaseDevice" to "no" in nasd.conf makes the problem go away.

2) The emu10k1 driver allows /dev/dsp to be opened multiple times (up to 
    4 or so times, I think), and it somehow will multiplex multiple incoming 
    streams.  So, "ReleaseDevice" isn't strictly necessary to make nasd
    co-exist with non-NAS software.  (Why didn't I realize this a year ago?
    Eh, lazy...)

   I think this feature of the sound driver is somehow triggering a bug in
    nasd when it comes to opening/reopening/re-reopening the dsp device.

-matt m.


----- End forwarded message -----
-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer