On 21/12/2007, Marcelo Boveto Shima <[EMAIL PROTECTED]> wrote: > > Included with some changes. There were some places that were using > /var/run/$NAME.pid > We have to take a closer look because I think the pidfile is created by > the > daemon itself not by start-stop-daemon.
Yes. I have played with this a little and it appears that libvirtd does not work properly when you try and supply --pid-file <file> to it. Even if you run it without start-stop-daemon, it never quite manages to start properly. I think this must be a bug in libvirtd. Since the --pid-file is an issue, I think it would be better to set the variables as follows in the init script: PIDDIR=/var/run/libvirt PIDFILE=/var/run/$NAME.pid rather than PIDDIR=/var/run/libvirt PIDFILE=$PIDDIR/$NAME.pid Can you please check if /var/lib/libvirt is provided by the package? After installing the latest version, I had to manually mkdir /var/lib/libvirt for the dnsmasq dhcpd.leases file to be created. P.S. I see that you have added /var/run/libvirt to the libvirt-bin package. I am not sure this is a good idea as /var/run is mounted in memory on boot, hence the need to mkdir $PIDDIR. -- [needs-packaging] virt-manager https://bugs.launchpad.net/bugs/116897 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
