Note that the 'nginx' package has the same issue, not just
postfix, and possibly other packages; really it's any package
that has required-start: $named in its init script.
(I dislike the rationale for that to begin with -- it should be
enough to require-start: $network and merely
should-start
severity 773170 important
--
On Wed, Dec 17, 2014 at 09:33:16AM +0100, Yves-Alexis Perez wrote:
On Tue, 16 Dec 2014 09:58:09 +0100 Petter Reinholdtsen p...@hungry.com
wrote:
Well, postfix uses Required-start: $named because it needs name
resolution. And I guess dnsmasq provides $named by
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
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
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
5 matches
Mail list logo
