[Bug 599342] Re: Temporary failure in name resolution

[Serge Hallyn]

This scares me because on my laptop, where I do still have

127.0.1.1       vostro2

in my /etc/hosts,  'host vostro2' returns 1.  So most stock ubuntu
installations would apparently wait forever to start libvirt-bin.

Does the following /etc/init/libvirt-bin.conf work for you?

==========================================================

description "libvirt daemon"
author "Dustin Kirkland <kirkland at canonical.com>"

start on runlevel [2345] and (started network-interface
          or started network-manager
          or started networking)
stop on runlevel [!2345]

expect daemon
respawn

pre-start script
	mkdir -p /var/run/libvirt
	# Clean up a pidfile that might be left around
	rm -f /var/run/libvirtd.pid
end script

# If you used to set $libvirtd_opts in /etc/default/libvirt-bin,
# change the 'exec' line here instead.


** Changed in: libvirt (Ubuntu Maverick)
       Status: Triaged => Incomplete

-- 
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.