From: Matthew Daley Date: Sun, 27 Oct 2013 06:49:14 +0000 (+1300) Subject: xl: don't emit misleading daemon pid message X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~6120 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=2cd1f418feb215c379b6737576b53bba6f70c1a6;p=xen.git xl: don't emit misleading daemon pid message After creating a domain, xl forks off a process to handle domain events (shutdown, disk eject, ...). It prints out the pid of the process created by the fork to stdout. However, the newly forked process soon after calls daemon(), which itself forks once more (and exit()s the original process). This means that the pid printed out is not the pid of the actual process which remains in the background after all is said and done, instead it is the pid of the transient process that exists between xl's fork() and the fork'd process's daemon() call. We could resolve this by printing the correct pid, ie. by open-coding daemon() (we already do most of the heavy lifting it does ourselves by fiddling with the standard fds). However, since no-one seems to be complaining about the misleading message to begin with, and since it seems like a pointless message anyway, just remove it outright instead. Signed-off-by: Matthew Daley Acked-by: Ian Jackson --- diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c index a8261be048..fddaa80dd8 100644 --- a/tools/libxl/xl_cmdimpl.c +++ b/tools/libxl/xl_cmdimpl.c @@ -2140,8 +2140,6 @@ start: child1 = xl_fork(child_waitdaemon); if (child1) { - printf("Daemon running with PID %d\n", child1); - for (;;) { got_child = xl_waitpid(child_waitdaemon, &status, 0); if (got_child == child1) break;