Bug 78542 - restrict time.nist.gov is bad
restrict time.nist.gov is bad
Status: CLOSED DUPLICATE of bug 70557
Product: Red Hat Raw Hide
Classification: Retired
Component: redhat-config-date (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-25 08:42 EST by Gene Czarcinski
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-25 08:42:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2002-11-25 08:42:49 EST
Description of Problem:
While redhat-config-date-1.5.5-1 is a start, the solution still needs work. 
Unfortuneately, as pointed out in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=70557
restrict needs ip numbers ... not a name.  Unless ntp is changed so restrict
looks up numbers or there is some other magic way to do what restrict
192.43.244.18 would do, this package will need to look up the ip-addr and plug
it into the restrict statement.

After applying 1.5.5-1 and running it to update /etc/ntp.conf, I looked in
/vat/log/messages and found:

ntpd[15033]: getnetnum: "time.nist.gov" invalid host number, line ignored

replacing "time.nist.gov" with "192.43.244.18" and restarting ntpd succeeded.
Comment 1 Gene Czarcinski 2002-11-25 09:42:43 EST

*** This bug has been marked as a duplicate of 70557 ***

Note You need to log in before you can comment on or make changes to this bug.