From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH 1/3] xenstored - postpone fork after
	initialization
Date: Thu, 27 Mar 2008 11:36:19 +0000
Message-ID: <C4113733.1E697%keir.fraser@eu.citrix.com>
References: <20080327112705.GA9173@wavehammer.waldi.eu.org>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20080327112705.GA9173@wavehammer.waldi.eu.org>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Bastian Blank <bastian@waldi.eu.org>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

By the way, were the xend startup changes required at all? getstatusoutput()
waits for the child process to exit, doesn't it?

 -- Keir

On 27/3/08 11:27, "Bastian Blank" <bastian@waldi.eu.org> wrote:

> On Thu, Mar 27, 2008 at 09:15:55AM +0000, Keir Fraser wrote:
>> In any case I think it's bad practice to daemonise after initialisation --
> 
> The daemons I just checked disagree with you. They want to provide
> errors if the initialization fails, which is only possible before the
> parent exits.
> 
>> Perhaps a better way to go would be to wait for the stdout pipe to be
>> half-closed? Or to pass switch -P to xenstored and wait for the daemon pid
>> to be written to the stdout pipe?
> 
> Well, find the real problem. In my tests it properly responds to the
> clients.
> 
> Bastian