Quoting Mikhail S Medvedev ([email protected]):
> So without the daemon, I would expect you should not be able to do
> '/etc/init.d/virtlockd start'. Why apt-get install is not failing for

systemctl start virtlockd works fine

now interestingly,

0 ✓ serge@sl ~ $ sudo systemctl stop virtlockd
[sudo] password for serge:
Warning: Stopping virtlockd.service, but it can still be activated by:

so it's supposed to be socket activated.  So if it's not getting
started when libvirt needs it, well that's messed up.

> you? What distro are you installing on? And can you confirm you are
> installing libvirt-bin=1.3.1-1ubuntu2?

ii  libvirt-bin                                          1.3.1-1ubuntu2
amd64        programs for the libvirt library

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547208

Title:
  package libvirt-bin=1.3.1-1ubuntu1 fails to install due to new
  virtlockd initd script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1547208/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to