From: "Chris Rankin" <rankincj@yahoo.com>
To: Sebastian Kapfer <sebastian_kapfer@web.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [BUG] alsa-lib leaves sound device open for child processes
Date: Wed, 5 Feb 2003 22:39:22 +0000 (GMT) [thread overview]
Message-ID: <20030205223922.80686.qmail@web40607.mail.yahoo.com> (raw)
In-Reply-To: <20030205205905.7800db0c.sebastian_kapfer@web.de>
--- Sebastian Kapfer <sebastian_kapfer@web.de> wrote:
> May I ask what the child process is supposed to to
> with a raw ALSA file
> descriptor? AFAICT, developers are supposed to use
> the alsa-lib API, and
> not write to FD's. So the underlying file descriptor
> looks to me like a
> mere implementation detail which 99% of all users
> shouldn't need to care about.
I consider this situation analogous to the
relationship between file descriptors and FILE*
pointers. By your argument, libc should probably set
the FD_CLOEXEC flag here, too. But it doesn't.
Chris
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next parent reply other threads:[~2003-02-05 22:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030205205905.7800db0c.sebastian_kapfer@web.de>
2003-02-05 22:39 ` Chris Rankin [this message]
2003-02-06 14:40 ` [BUG] alsa-lib leaves sound device open for child processes Sebastian Kapfer
2003-02-06 23:10 ` Chris Rankin
2003-02-07 13:03 ` Paul Davis
2003-02-07 13:58 ` Chris Rankin
2003-02-07 15:22 ` Paul Davis
2003-02-07 16:13 ` Takashi Iwai
2003-02-07 19:54 ` Chris Rankin
2003-02-07 14:37 ` Sebastian Kapfer
2003-02-07 19:46 ` Chris Rankin
2003-02-08 11:50 ` Jaroslav Kysela
2003-02-08 13:55 ` Sebastian Kapfer
2003-02-08 19:45 ` Sebastian Kapfer
2003-02-08 19:53 ` Jaroslav Kysela
2003-02-12 11:54 ` Takashi Iwai
2003-02-12 12:46 ` Jaroslav Kysela
2003-02-07 19:35 Chris Rankin
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 18:50 Chris Rankin
2003-02-03 22:16 Sebastian Kapfer
2003-02-05 11:20 ` Jaroslav Kysela
2003-02-05 12:42 ` Takashi Iwai
2003-02-05 13:05 ` Jaroslav Kysela
2003-02-05 13:55 ` Takashi Iwai
2003-02-05 14:03 ` Chris Rankin
2003-02-05 14:16 ` Paul Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030205223922.80686.qmail@web40607.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=sebastian_kapfer@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.