On Mon, Nov 02, 2009 at 05:05:55PM -0500, Cole Robinson wrote:
> On 10/23/2009 09:05 AM, Daniel P. Berrange wrote:
> > The daemonizing code lets the parent exit almost immediately. This
> > means that it may think it has successfully started even when
> > important failures occur like not being abl
On 10/23/2009 09:05 AM, Daniel P. Berrange wrote:
> The daemonizing code lets the parent exit almost immediately. This
> means that it may think it has successfully started even when
> important failures occur like not being able to acquire the PID
> file. It also means network sockets are not yet
On Sat, Oct 31, 2009 at 02:29:42PM +0100, Laurent L?onard wrote:
> Hi,
>
> I'm not a C expert, but I see there is a use of an unitialized variable:
>
> default:
> {
> int got, exitstatus = 0;
> int ret;
> char status;
>
> close(statuspi
Hi,
I'm not a C expert, but I see there is a use of an unitialized variable:
default:
{
int got, exitstatus = 0;
int ret;
char status;
close(statuspipe[1]);
/* We wait to make sure the first child forked successfully */
On Thu, Oct 29, 2009 at 03:29:38PM +, Daniel P. Berrange wrote:
> On Thu, Oct 29, 2009 at 04:19:47PM +0100, Daniel Veillard wrote:
> > On Fri, Oct 23, 2009 at 02:05:39PM +0100, Daniel P. Berrange wrote:
> > > The daemonizing code lets the parent exit almost immediately. This
> > > means that it
On Thu, Oct 29, 2009 at 04:19:47PM +0100, Daniel Veillard wrote:
> On Fri, Oct 23, 2009 at 02:05:39PM +0100, Daniel P. Berrange wrote:
> > The daemonizing code lets the parent exit almost immediately. This
> > means that it may think it has successfully started even when
> > important failures occu
On Fri, Oct 23, 2009 at 02:05:39PM +0100, Daniel P. Berrange wrote:
> The daemonizing code lets the parent exit almost immediately. This
> means that it may think it has successfully started even when
> important failures occur like not being able to acquire the PID
> file. It also means network so
On Wed, Oct 28, 2009 at 06:52:49PM +, Daniel P. Berrange wrote:
> On Wed, Oct 28, 2009 at 03:22:38PM +0100, Guido G?nther wrote:
> > Hi Daniel,
> > On Fri, Oct 23, 2009 at 02:05:39PM +0100, Daniel P. Berrange wrote:
> > > The daemonizing code lets the parent exit almost immediately. This
> > >
On Wed, Oct 28, 2009 at 03:22:38PM +0100, Guido G?nther wrote:
> Hi Daniel,
> On Fri, Oct 23, 2009 at 02:05:39PM +0100, Daniel P. Berrange wrote:
> > The daemonizing code lets the parent exit almost immediately. This
> > means that it may think it has successfully started even when
> > important fa
Hi Daniel,
On Fri, Oct 23, 2009 at 02:05:39PM +0100, Daniel P. Berrange wrote:
> The daemonizing code lets the parent exit almost immediately. This
> means that it may think it has successfully started even when
> important failures occur like not being able to acquire the PID
> file. It also means
The daemonizing code lets the parent exit almost immediately. This
means that it may think it has successfully started even when
important failures occur like not being able to acquire the PID
file. It also means network sockets are not yet open.
To address this when daemonizing the parent passes
11 matches
Mail list logo