Bug 58389 - ntp time correct, but syslog is still old time
Summary: ntp time correct, but syslog is still old time
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd   
(Show other bugs)
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-15 16:57 UTC by Stephen Lawrence Jr.
Modified: 2007-04-18 16:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-07 23:13:05 UTC
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.)

Description Stephen Lawrence Jr. 2002-01-15 16:57:35 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914

Description of problem:
After configuring ntp, and getting my machines time syncronized, I noticed my
syslog entries still had the old timestamp on them. I had to restart syslog
manually to get it to recognize the new time.

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


How reproducible:
Always

Steps to Reproduce:
1.set time to bogus time using 'date'
2.restart syslogd
3./etc/rc.d/init.d/ntpd restart
4. check system date 'date' which should be ntpd sync'd date now
3.check /var/log/messages for entries with "bogus" time
	

Actual Results:  Bogus time showed.

Expected Results:  date/time from ntp server should show on all log files

Additional info:
Comment 1 Jason Vas Dias 2005-06-07 23:13:05 UTC 
Very sorry this bug seems to have escaped attention for so long -
I've recently taken over maintenance of the sysklogd package.

This bug is definitely fixed with all current sysklogd/glibc/ntpd
versions (unable to determine which component originally caused this
bug. Closing out.
Note You need to log in before you can comment on or make changes to this bug.