[patch] Out of the box NTP support (on FreeBSD)

[Kenneth Porter]

--On Tuesday, August 05, 2003 12:13 PM +0200 Roderick van Domburg
<r.s.a.vandomburg at student.utwente.nl> wrote:

> Hmm, that does seem to be a good idea. Basically, every interested 
> service could provide it's own "dhclient.conf" look-a-like requesting 
> the relevant options. Unlike the /etc/dhclient.conf however, their 
> behavior would be to add up all the requested options instead of 
> overriding them.

There would also need to be some way for them to get notified when a value was
updated (and presumably when the interface first comes up). There's also a
chicken-and-egg issue at boot time, when the service may not be up when the
notification is sent. This is where the service should supply a script to
process the notification.

For instance, a script for ntp would update its config file, then issue
"service ntp condrestart". (How would the options be made available to the
script?)

So we need two directories, one for options to request and one for callback
scripts. Or the callback script could be invoked with a parameter to make it
echo the list of needed options to stdout, and another to process the received
options, similar to the way initscripts have standard parameters
start/top/restart.