[pkg-ntp-maintainers] Bug#683061: Bug#683061: ntp: diff for NMU version 1:4.2.6.p5+dfsg-2.1

Ivo De Decker ivo.dedecker at ugent.be
Sun Aug 26 19:21:10 UTC 2012


Hi,

On Sun, Aug 26, 2012 at 09:03:04PM +0200, Kurt Roeckx wrote:
> > > > +  * Add init script dependency on $named, based on report from Helmut Grohne
> > > > +    (closes: #683061)
> > > That does not make any sense at all.  ntp can perfectly work
> > > without named installed, and it works if named is started after
> > > ntpd.
> > 
> > Well, there are quite a few init scripts on my machine with
> > Required-Start: $named, and not a single one providing $named, and I
> > also have no nameserver installed ...
> 
> bind9 doesn't seem to be providing it either.  So this looks like
> it isn't doing anything in any of those scripts, and that the
> patch is unlikely to fix anything?
> 
> I would assume if it declares a Required-Start, that that service
> should actually exist and be started, and that if it's not
> available that the package having such a Required-Start is
> buggy because it's not having a proper Depends.

$named is a virtual facility:
http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/facilname.html

$named:	 	
IP name-to-address translation, using the interfaces described in this
specification, are available to the level the system normally provides them.
Example: if a DNS query daemon normally provides this facility, then that
daemon has been started. 

Please note that '$named' does not mean 'bind'.

There are a number of packages with init scripts that have "Required-Start:
$named" (cron, apache2, postfix to name a few), so having that certainly isn't
a bug.


Cheers,

Ivo



More information about the pkg-ntp-maintainers mailing list