On Tue, May 20, 2008 at 12:02:03PM -0400, Daniel Veillard wrote:
> On Fri, May 16, 2008 at 05:39:46PM +0100, Daniel P. Berrange wrote:
> > On Fri, May 16, 2008 at 05:05:08PM +0100, Daniel P. Berrange wrote:
> > There were actually some more changes needed. It needs to write the PID file
> > even if
On Fri, May 16, 2008 at 05:39:46PM +0100, Daniel P. Berrange wrote:
> On Fri, May 16, 2008 at 05:05:08PM +0100, Daniel P. Berrange wrote:
> > When used with the --daemon arg, libvirtd will write out a pid file to
> > /var/run/libvirtd.pid and exit if this file already exists. Unfortuantely
> > it d
On Fri, May 16, 2008 at 05:05:08PM +0100, Daniel P. Berrange wrote:
> When used with the --daemon arg, libvirtd will write out a pid file to
> /var/run/libvirtd.pid and exit if this file already exists. Unfortuantely
> it does this quite late in its startup procedure - in particular *after*
> the c
On Fri, 16 May 2008, Daniel P. Berrange wrote:
> When used with the --daemon arg, libvirtd will write out a pid file to
> /var/run/libvirtd.pid and exit if this file already exists. Unfortuantely
> it does this quite late in its startup procedure - in particular *after*
> the call to qemudInitiali
When used with the --daemon arg, libvirtd will write out a pid file to
/var/run/libvirtd.pid and exit if this file already exists. Unfortuantely
it does this quite late in its startup procedure - in particular *after*
the call to qemudInitialize(), which in turns initializes the drivers,
which in t
