On Wed, 17 Dec 2014 09:33:16 +0100 Yves-Alexis Perez <cor...@debian.org> wrote: > On Tue, 16 Dec 2014 09:58:09 +0100 Petter Reinholdtsen <p...@hungry.com> wrote: > > > > Control: reassign -1 postfix > > > > [Salvo Tomaselli] > > > Dear Maintainer, > > > > > > insserv refuses to start postfix at boot, because I have configured dnsmasq > > > to be disabled. > > > > Hi. As insserv is not involved at all during boot, I suspect this bug > > is misfiled. Perhaps it is a problem with postfix or dnsmasq > > dependencies (should be soft, not hard) or with systemd refusing to > > start. My prime suspect would be postfix, so I pass this bug over to > > the postfix maintainers for a closer look. If postfix do not require > > dnsmasq (but should be startet after it if it exist) it should only use > > should-start instead of require-start in its init.d script. > > > > Well, postfix uses Required-start: $named because it needs name > resolution. And I guess dnsmasq provides $named by default, but that's > actually not the case in Salvo system. Not sure what's the correct way > to fix this. A quick way would be to remove the "Provide: $named", when > configuring dnsmasq to not be be used as a name resolution daemon, but > that can't really be done automatically.
So the bug in postfix is that it fails to start when a service that claims to provide $named doesn't actually provide it? Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
