Bug 81564 - error from initscript when using hostnames for servers
error from initscript when using hostnames for servers
Product: Red Hat Raw Hide
Classification: Retired
Component: ntp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-01-10 10:46 EST by Tim Waugh
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-30 11:10:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2003-01-10 10:46:53 EST
Description of problem:
The initscript gives errors:

ntpd: Removing firewall opening for ntp.demon.co.uk port 123iptables: Bad rule
(does a matching rule exist in that chain?)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Use 'server hostname.domain.whatever' in ntp.conf
2. service ntp restart
Actual results:

Expected results:
No errors.

Additional info:
It could either ignore non-IP entries, or (better) use dig to figure out the IP
addresses for each hostname; in the latter case it needs to start up after named
of course.
Comment 1 Harald Hoyer 2003-01-30 11:10:30 EST
1. hostnames are not safe and the name server could be down... not reliable.
2. maybe ntpd is not running anymore or your firewall was modified in the meantime
I could direct error messages to /dev/null, but this is not intended..

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