Regarding compiling BIND 9.10.3-p4 on a SystemD Distro

[Lightner, Jeff]

It doesn't.   The systemd script either succeeds or fails.   Any script that is dependent on it succeeding won't start.   

Again it is a change.  

In init you'd see a start had failed (or was hung).  

In systemd it simply sends the instruction to start everything that is supposed to start.   The upside of this approach is that the rest of your startup succeeds as it run asynchronously unless you've included a dependency for the thing that failed.    It also means a hung script doesn't stop your boot in its tracks like it did in init.   You can login and troubleshoot things.

The downside is you don't get the pretty display showing OK or FAILED for each script during boot because boot completing is NOT dependent on ALL scripts succeeding.

If it is important to you that certain things be up you need to set up monitoring.  We do that with Nagios here.

-----Original Message-----
From: Tony Finch [mailto:fanf2 at hermes.cam.ac.uk] On Behalf Of Tony Finch
Sent: Wednesday, March 23, 2016 9:52 AM
To: Lightner, Jeff
Cc: bind-users at lists.isc.org
Subject: RE: Regarding compiling BIND 9.10.3-p4 on a SystemD Distro

Lightner, Jeff <JLightner at dsservices.com> wrote:
>
> With systemd the methodology isn't that BIND notifies other things 
> that it is up.  It is that other things, if dependent upon BIND, have 
> in their systemd files a requirement that BIND be up before they start.

Yes, but how does systemd know when BIND is up?

(The Red Hat and five-ten-sg RPMs don't seem to have an answer.)

Tony.
--
f.anthony.n.finch  <dot at dotat.at>  http://dotat.at/  -  I xn--zr8h punycode Dogger, Fisher, German Bight, Humber: Northwest backing southwest 3 or 4, increasing 5 at times. Slight, occasionally moderate. Fog patches, rain at times. Moderate or good, occasionally very poor.