Bug 667524 – update ntp.conf to include 4 servers by default to match fedora and best practices

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 667524 - update ntp.conf to include 4 servers by default to match fedora and best practices

Summary:	update ntp.conf to include 4 servers by default to match fedora and best prac...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	ntp (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	Unspecified Unspecified

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Miroslav Lichvar
QA Contact:	qe-baseos-daemons
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	947775 994199
	Show dependency tree / graph

Reported:	2011-01-05 16:07 EST by Jeremy Eder
Modified:	2013-11-21 15:02 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:	ntp-4.2.6p5-1.el6
Doc Type:	Enhancement
Doc Text:	Feature: Use four servers instead of three in the default ntp.conf. Reason: Better reliability of the NTP service. Result (if any):
Story Points:	---
Clone Of:
Clones:	994199 (view as bug list)
Environment:
Last Closed:	2013-11-21 04:48:52 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2013:1593	normal	SHIPPED_LIVE	ntp bug fix and enhancement update	2013-11-20 16:39:27 EST

Groups: None (edit)

Comment 2 RHEL Product and Program Management 2011-01-07 10:45:54 EST

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 RHEL Product and Program Management 2011-07-05 20:21:29 EDT

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 5 Suzanne Yeghiayan 2012-02-14 18:05:50 EST

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 9 errata-xmlrpc 2013-11-21 04:48:52 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1593.html

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