On a): what I meant here is not that libvirt should catch all cases of itself disappearing, but rather that the other daemons don't have a rm on the .pid file; I didn't check what the other daemons to, I guess they are checking for a running process with that pid and whether it's the same program before aborting, and overwriting the pid file otherwise.
It just strikes me that we don't have rm /var/run/<program>.pid in the other upstart jobs, and it's something which should be dealt with by the upstream logic, isn't it?
Of course I'm fine with a simple rm for lucid release as I understand there's little time to developer upstream fixes at this point!
On a): what I meant here is not that libvirt should catch all cases of itself disappearing, but rather that the other daemons don't have a rm on the .pid file; I didn't check what the other daemons to, I guess they are checking for a running process with that pid and whether it's the same program before aborting, and overwriting the pid file otherwise.
It just strikes me that we don't have rm /var/run/ <program> .pid in the other upstart jobs, and it's something which should be dealt with by the upstream logic, isn't it?
Of course I'm fine with a simple rm for lucid release as I understand there's little time to developer upstream fixes at this point!