|
|
|
|
google site
|
|||||||
| Forums | Register | Blog | Man Pages | Forum Rules | Links | Albums | FAQ | Users | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
![]() |
|
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|||
|
All command line utilities use time() which reads the kernel's internal timestamp - it is accurate to one second, it returns a time_t value of the the elapsed seconds since the start of the epoch. Does this affect file times as well? Code:
date ; touch t.lis; ls -l t.lis If so, then something is wrong. |
| Sponsored Links |
|
|
|
|||
|
Here's the output, file times are not affected.
Quote:
This is not good! |
|
||||
|
It looks like Linux tracks the number of clock ticks (called jiffies on linux
) since the system boot. Processes are time stamped with this count. ps obtains the boottime and adds in the clock ticks to get a process' start time. Somehow that calculation is wrong in your case. Since your system was booted, you seem to have had at least 9 minutes and 38 seconds worth too many clock ticks. How long has your system been up? Maybe the clock is just running way too fast. Are you using ntp to keep it in sync? Or do you manually reset the clock when it is off? Ideally, ntp is supposed to detect a clock that has a consistently incorrect frequency and compensate for it. Maybe your ntpd is broken. Or you might have some jiffie-wrap. Or you might have some kernel bug that corrupted your boottime variable. All I can suggest is a reboot. |
|
|||
|
Yeah syncing with ntp doesnt seem to have any effect. My system has only been up 45 days, so to be that out of sync seems crazy in such a short time. Hopefully its not a kernel bug, but I wont rule it out. In fact its probably a good place to start searching for a fix if a reboot doesnt do it. Thanks all.
|
|
|||
|
I just wanted to let you all know that I have rebooted the server (about a week ago) and am still having the same issue. Code:
date;ps -ef|grep date Mon Jan 2 10:37:12 EST 2006 root 13993 13851 0 10:39 pts/38 00:00:00 grep date Kernel: 2.6.5-1.358smp I dont think it will be impacting anything, but its just not nice to see. I will probably be looking to upgrade my kernel sooner than expected. Thanks again fellas! |
|
|||
|
This is just a suggestion and i don't know really much about Linux, but:
On AIX ntp writes to the files /etc/ntp.trace and /etc/ntp.drift (yes, silly idea to put a logfile into /etc, but I'm not responsible for it), maybe your ntp writes there (or somewhere similar) too. Maybe it helps to check out these files. bakunin |
|
|||
|
Try 'dmesg', see anything interesting?
|
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Tags |
| linux, solaris |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Get date and time for past 1 hour from current date | spch2o | Shell Programming and Scripting | 5 | 08-29-2008 05:32 AM |
| Processing a log file based on date/time input and the date/time on the log file | primp | Shell Programming and Scripting | 4 | 03-16-2008 11:23 AM |
| Date/Time help | ssmiths001 | Shell Programming and Scripting | 5 | 01-27-2006 03:40 AM |
| X Keyboard Extension version mismatch | hiker04 | Solaris | 0 | 09-13-2005 09:51 AM |
| time and date in os X help please | dercarcort | UNIX for Dummies Questions & Answers | 1 | 06-30-2002 09:03 AM |