[ntp:security] [Bug 2960] upgrade to 4.2.8p4 causes FAIL at name resolution; error: ntpd[9881]: giving up resolving host clock.isc.org: Servname not supported for ai_socktype (-8)

bugzilla-daemon at ntp.org bugzilla-daemon at ntp.org
Tue Feb 9 11:39:58 UTC 2016


https://bugs.ntp.org/show_bug.cgi?id=2960

--- Comment #23 from Reinhard Max <max at suse.com> 2016-02-09 11:39:58 UTC ---
(In reply to comment #22)

> It might be best to make the distinction between forking and threading DNS
> worker a runtime decision instead of a compile time issue.

A few more questions about that:

1. Are threads (or forking workers) being used for anything else than async
DNS?

2. What are the downsides of running async DNS as a forking worker and do they
justify the additional complexity to make it a runtime decision?

3. If the downsides are tolerable, how about making the default dependent on
the target system (forking where name resolution is known not to play well with
chroot, threading elsewhere) if that helps to keep the code simpler?

> It would also need to fork away the worker rather early (before entering
> the root jail), and that would in turn need quite some work to keep the
> pipe handles.

Where in the code and/or documentation can I read up on this?

-- 
Configure bugmail: https://bugs.ntp.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the security mailing list