[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/3] xenstored - postpone fork after initialization


  • To: Bastian Blank <bastian@xxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 27 Mar 2008 11:36:19 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 27 Mar 2008 04:37:38 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciP/sY2BP7PkvvyEdyKuwAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH 1/3] xenstored - postpone fork after initialization

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@xxxxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.