Bug 110018

Summary:	iptables should restart ntpd when iptables is restarted
Product:	[Retired] Red Hat Linux	Reporter:	Joseph Shraibman <jks>
Component:	iptables	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	Ben Levenson <benl>
Severity:	low	Docs Contact:
Priority:	medium
Version:	9
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-18 11:08:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joseph Shraibman 2003-11-14 01:08:00 UTC

Description of problem:
When I run /etc/rc.d/init.d/iptables restart I break ntpd.  I suggest
the iptables script on (re)start checks the status of ntpd, and if
ntpd is running it should restart ntpd (or at least print a warning
message)

Version-Release number of selected component (if applicable):
iptables-1.2.7a-2

How reproducible:
always

Steps to Reproduce:
1. /etc/rc.d/init.d/iptables restart
2. wait awhile
3. /usr/sbin/ntpq -c peers
  
Actual results:
ntpd losses sync with upstream servers

Additional info:
Should be trivial shell script change. /etc/rc.d/init.d/ntpd status
exits with an error code if ntpd is not running. I could do it myself
if asked.

Comment 1 Thomas Woerner 2005-11-18 11:08:23 UTC

Please open ntp ports for your ntp servers in the iptables configuration.
There is no way that ipatbles can restart other services and this might not be a
good idea for some services.

Closing as NOTABUG.