nptd hangs forever if hostname can't be resolved

Grant Edwards grant.b.edwards at gmail.com
Thu Oct 12 19:08:08 UTC 2017


I've run into a problem where ntpd is given a peer name it can't
resolve.

It never goes into the backgroud and becomes a daemon.

Instead it retries forever in the foreground, stopping systgem startup
and printing this on the console every few seconds:

  ntpd: bad address 'asdf.asdf'
  ntpd: bad address 'asdf.asdf'
  ntpd: bad address 'asdf.asdf'
  [...]

This seems rather, um, unhelpful.  Notice that I didn't pass the '-n'
option telling it "do not daemonize".  So I naively expected it to
daemonize.

What's the "right" way to start up ntpd from /etc/init.d/<whatever>?

-- 
Grant Edwards               grant.b.edwards        Yow! Catsup and Mustard all
                                  at               over the place!  It's the
                              gmail.com            Human Hamburger!



More information about the busybox mailing list