Jerome ALET wrote:
> On Thu, 10 Jun 1999, Ronan Demoment wrote:
> > > > I have also the same problem and I tried to remove the /sbin/update in inittab
> > > > but it didn't solve the problem. I also tried kernels 2.2.5 and 2.2.9.
> > > > I have an SBAWE32 which is very similar to SBAWE64. Maybe it cames from that
> > > > soundcard. Does anyone has the same problem with another soundcard? does anyone
> > > > has an AWE32/64 and no problem?
>
> Excuse me because I don't use Kde nor Kaudioserver, nor even an AWE64.
> However there's probably some perms problem on /dev/dsp, /dev/audio and
> others.
>
> in /etc/security/console.perms the sound package perms are set, but
> probably we should set them to 0666 0666 instead of the very restricted
> ones.
>
> I encountered sound problems here (impossible to open some sound device
> from time to time): I've chmod 666 /dev/audio and others but the problem
> still occured from time to time. Now I've modified
> /etc/security/console.perms and I've got no problem anymore.
>
> I don't know exactly when /etc/security/console.perms is scanned but I
> suspect the problem happens when a user is connected, say in X, and root
> logs in on a text console, then the audio devices become unavailable to
> the user.
>
> Maybe I'm wrong but AFAIK my sound problem is solved, so maybe this should
> help you: maybe your kaudioserver hanging problem comes from it loosing
> perms to access audio devices.
>
> bye,
> Jerome
ok, setting 666 permission to sound devices in /etc/security/console.perms solves the
problem of sound and unmounting / at shutdown. But i'm not sure this is the right way
to
do it since it allows any user to use audio devices even when another one is owns it
(i'm not very familiar with linux but i think this is what means 666 on the sound
devices). Maybe the source of the problem comes from that even after deconnexion of an
ordinary user, sound devices are still owned by him. Should not be these devices be
released to root after use? (i hope not to say too big mistakes)
