From: Takashi Iwai Subject: Re: dmix in a forked process Date: Tue, 05 Aug 2008 11:53:19 +0200 Message-ID: References: <4eccebac0808012003j49ea4351pc34f3f1ed7690f15@mail.gmail.com> <4eccebac0808021945s66b362e3u51ecedea830a04e4@mail.gmail.com> <4eccebac0808031347v26c5c430h2e66f0439e64fbdf@mail.gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (ns.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id 2B1E110383E for ; Tue, 5 Aug 2008 11:53:22 +0200 (CEST) In-Reply-To: <4eccebac0808031347v26c5c430h2e66f0439e64fbdf@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Bankim Bhavsar Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Sun, 3 Aug 2008 13:47:34 -0700, Bankim Bhavsar wrote: > > On Sun, Aug 3, 2008 at 11:38 AM, Jaroslav Kysela wrote: > > On Sat, 2 Aug 2008, Bankim Bhavsar wrote: > > > >> I'm currently porting the sound code of our app from OSS to ALSA but > >> this problem is preventing me from doing so. > >> Is there any way to get around this problem? > > > > What's your problem with fork()? > > If our app is the first to start dmix then a copy of the process (app) > will remain till > the last application closes the share device. Right. At least, its resources remain. > So our problem is not fork but fork without *exec*. And what is your problem more exactly? We may create a small binary to do exec for the dmix server if this really matters. Or, an easier fix is to use more recent kernels. Then there is no longer fork for dmix. Takashi