On Wed, Dec 10, 2008 at 11:27:53AM +0530, Shwetha Srinivasan - Sun Microsystems
- Bangalore India wrote:
> Hi,
> I have a certain escalation where the customer doesn't have NTP working
> right because it cannot resolve host names. This happens because the DNS
> service is not necessarily started before the NTP service, leaving it
> unable to resolve hostnames. I have tried to fix this by adding a
> dependency on name-services (in ntp.xml) as follows :
>
> <dependency name='name-services'
> grouping='require_any'
> restart_on='error'
> type='service'>
> <service_fmri value='svc:/milestone/name-services' />
> </dependency>
>
> While reviewing this fix, Brian suggested that in the future, many
> customers will want to deploy DNSSEC which requires NTP to be running
> before the service is initialized. As an alternative, he suggests that
> we either
> - have two services or
> - have the start method query SMF for the status of the milestones -
> this alternative has the advantage of letting us look at the conf file
> and do the right thing dynamically.
>
> Any thoughts from the experts on this ?
Perhaps it's time to look at upgrading NTPd? Later versions defer
lookups when DNS is unavailable and retry at a later point.
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20081210/2effdfce/attachment.bin>
