Your message dated Tue, 11 Nov 2008 17:26:31 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Pkg-libvirt-maintainers] Bug#504605: libvirt-bin:
README.Debian says dnsmasq should not be already running
has caused the Debian Bug report #504605,
regarding libvirt-bin: README.Debian says dnsmasq should not be already running
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
504605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504605
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libvirt-bin
Version: 0.4.6-4
Severity: normal
From /usr/share/doc/libvirt-bin/README.Debian:
| In order for things to work this way you need to have the recommended
packages
| dnsmasq, bridge-utils and iptables installed and dnsmasq must not be already
| running since libvirt starts it with the above parameters.
In my system dnsmasq was previously installed and running; nevertheless
libvirt-bin's own dnsmasq started normally, and served well the guests,
because it only listened in the bridge interface.
Cheers,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Truth is the most valuable thing we have, so let's economize it.
-- Mark Twain
--- End Message ---
--- Begin Message ---
On Tue, Nov 11, 2008 at 01:21:02PM +0100, Adeodato Simó wrote:
> I have interface=lo in my dnsmasq.conf, plus "bind-interfaces". However
> you are right that stopping or restarting the main dnsmasq with the
> init.d scripts kills the libvirt-bin dnsmasq, because the init.d script
> kills all existing dnsmasq's (it assumes them to be children of the main
> dnsmasq, and not standalone instances).
So that would be a bug in dnsmasq then? Anyways, I think leaving the
warning as is is fine since people might run into problems otherwise.
Cheers,
-- Guido
--- End Message ---
