Subject: RE: [linux-audio-dev] OSS question
From: STEFFL, ERIK *Internet* (SBCSI) ("STEFFL,)
Date: Tue Jul 31 2001 - 22:50:45 EEST
> -----Original Message-----
> From: Richard Guenther [mailto:rguenth_AT_tat.physik.uni-tuebingen.de]
> Sent: Tuesday, July 31, 2001 1:25 AM
> To: 'linux-audio-dev_AT_music.columbia.edu'
> Subject: RE: [linux-audio-dev] OSS question
>
>
> On Mon, 30 Jul 2001, STEFFL, ERIK *Internet* (SBCSI) wrote:
>
> > > Iain Sandoe schrieb:
> > > >
> > > > I wrote:
> > > > >> Do I have to setup a signal handler for SIGTERM to close
> > > the audio
> > > > >> device properly?
> > > > >
> > > > > This shouldn't be necessary either.
> > > >
> > > > Ok a replied too quickly - it is (only) when you get
> > > SIGTERM that you have
> > > > the problem?
> > > >
> > >
> > > I am sorry, actually it is a SIGKILL :(
> > > But a SIGTERM makes no difference.
> >
> > you cannot catch SIGKILL, but generally you shouldn't
> kill application
> > using SIGKILL (only if it does not respond to SIGTERM) -
> precisely for that
> > reason - it does not have a chance to exit gracefully.
> >
> > as for you problem - I guess setting a signal handler
> that closes audio
> > device (if still opened!) is the right way to go. It should
> be done by the
> > default exit routine though so I am not sure if you gain anything.
>
> You're on a UNIX system, so the kernel generally cleans up after you
> (i.e. it closes open fds, frees your memory, etc.), so if
> your soundcard
> /driver is not happy with being SIGKILLed then thats a driver bug I'd
> report to the appropriate place.
he was complaining about timing (soundcard device is actually closed about
2 s after program exits). if he closes device explicitly in program it might
happen (significantly for him) sooner than when the default exit routine
does it (or kernel).
erik
This archive was generated by hypermail 2b28 : Tue Jul 31 2001 - 22:51:50 EEST