a) shouldn't libvirtd handle this by itself as the other daemons do? I realize upstart is in the proper position to know that the service crashed, but upstart doesn't care about the pid file
b) perhaps this: [ -f /var/run/libvirtd.pid ] && rm -f /var/run/libvirtd.pid could simply be: rm -f /var/run/libvirtd.pid c) pidof /usr/sbin/libvirtd seems fragile to me; upstart must really have a good reason if it starts the libvirt-bin job; either this tests for an upstart bug, or this might match a locally started libvirtd; in either case, I don't think this test is needed. -- error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid' : File exists https://bugs.launchpad.net/bugs/510658 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
