Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 250373 - syslog time warp. kernel, sysklogd-1.4.2-8.fc7
syslog time warp. kernel, sysklogd-1.4.2-8.fc7
Status: CLOSED DUPLICATE of bug 249857
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-01 02:44 EDT by vikram goyal
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-01 10:24:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages (56.57 KB, text/plain)
2007-08-01 02:44 EDT, vikram goyal
no flags Details

  None (edit)
Description vikram goyal 2007-08-01 02:44:03 EDT
Description of problem:
syslog time is wrong (+5 hours in future) under kernel

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Pasting term's copy/paste of some sanity checks.
[root@f7host ~]# date
Wed Aug  1 12:08:33 IST 2007
[root@f7host ~]# ls -l --full-time sanitytest
ls: cannot access sanitytest: No such file or directory
[root@f7host ~]# time touch sanitytest

real    0m0.003s
user    0m0.001s
sys     0m0.002s
[root@f7host ~]# ls -l --full-time sanitytest
-rw-r--r-- 1 root root 0 2007-08-01 12:08:43.000000000 +0530 sanitytest
[root@f7host ~]# date
Wed Aug  1 12:08:53 IST 2007
[root@f7host ~]#
problem shows only in system logs till now.
Comment 1 vikram goyal 2007-08-01 02:44:03 EDT
Created attachment 160399 [details]
Comment 2 Catalin Muresan 2007-08-01 04:33:00 EDT


or update to the latest (may have been pushed in the mean time)

this fixed the time problem for me.
Comment 3 Chuck Ebbert 2007-08-01 10:24:15 EDT

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

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