From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [BUG] alsa-lib leaves sound device open for child processes Date: Wed, 05 Feb 2003 13:42:31 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20030203231629.26ee7464.sebastian_kapfer@web.de> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Jaroslav Kysela Cc: Sebastian Kapfer , "alsa-devel@lists.sourceforge.net" List-Id: alsa-devel@alsa-project.org At Wed, 5 Feb 2003 12:20:23 +0100 (CET), Jaroslav wrote: > > Well, I and Abramo think that it's better to force application developers > to clean allocated things before they'll call exec(). the problem is not only the explicit exec() call. without this bit, you'll pass the fds to other processes even by popen() or system() or whatever. that is, if your application calls an external program in the middle, it can block the operation. i don't see any critical drawback of setting FD_CLOEXEC as default. the application which needs to pass the alsa-lib's fds _explicitly_ can reset the bit via fcntl() again before calling exec(). Takashi ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com