From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastian Blank <bastian@waldi.eu.org>
Subject: Re: [PATCH 1/3] xenstored - postpone fork after
	initialization
Date: Thu, 27 Mar 2008 12:27:05 +0100
Message-ID: <20080327112705.GA9173@wavehammer.waldi.eu.org>
References: <20080326110016.GA20300@wavehammer.waldi.eu.org>
	<C411164B.1E676%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <C411164B.1E676%keir.fraser@eu.citrix.com>
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: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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

-- 
Killing is stupid; useless!
		-- McCoy, "A Private Little War", stardate 4211.8