
28 Oct
2009
28 Oct
'09
2:22 p.m.
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 network sockets are not yet open. With this patch applied to 0.7.2 I'm seeing:
# libvirtd -d 15:20:22.457: error : main:2971 : Failed to fork as daemon: Success about every second time I start the daemon. Any idea where this comes from? Cheers, -- Guido