07-21-2018
Maybe a slightly different question will resolve your current problem... Why not run ntpd to keep your clock in sync with an NTP server? That should keep jumps in time to jumps of less than a second instead of jumps of more than a quarter of an hour.
Or are you saying that the clock circuit on your system is so screwed up that it is bouncing forwards and backwards by large amounts and ntpd can't keep up?
10 More Discussions You Might Find Interesting
1. AIX
Hello Everyone,
I have a Domino application running on AIX 5.3 that does time conversions worldwide. It uses the operating system time as a reference for the conversion. My problem is that I need the AIX OS clock to be a 12 hour clock (AM/PM) rather than a 24 hour clock. I have tried the date... (2 Replies)
Discussion started by: RTwitchell
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Is there a chance that the clock() call returns 0 eternally???
Using BSD. My RTOS application freezes inconsistently only on particular hosts. When debugging it, I came to see that the RTOS timer does not tick at times. The underlying system call is clock() & it always returns zero when the... (4 Replies)
Discussion started by: smanu
4 Replies
3. UNIX for Advanced & Expert Users
Hi,
Ho do I differentiate system call from library call?
for example if I am using chmod , how do I find out if it is a system call or library call?
Thanks
Muru (2 Replies)
Discussion started by: muru
2 Replies
4. Programming
Hi all,
I am facing a problem in recv() system call i.e.. in my project i have to implement timer for sending (data) and resending purpose when there is no acknowledgement.
is there any way that recv() sys call has its own timer i.e., for ex: recv() has to wait for 10 secs.
if any... (0 Replies)
Discussion started by: Rohil
0 Replies
5. Programming
Hi all,
I am facing a problem in recv() system call i.e.. in my project i have to implement timer for sending (data) and resending purpose when there is no acknowledgement.
is there any way that recv() sys call has its own timer i.e., for ex: recv() has to wait for 10 secs.
if any one knows... (2 Replies)
Discussion started by: Rohil
2 Replies
6. Shell Programming and Scripting
Hi,
I currently use the ntpdate and date command to sync the internal clock source of my Solaris systems to the primary domain controller.
admin@myserver # ntpdate -d -u 192.168.???.???
14 Jan 17:42:02 ntpdate: ntpdate 3-5.93e+sun 03/06/05 23:16:45 (1.4)
transmit(192.168.???.???)... (2 Replies)
Discussion started by: jamba1
2 Replies
7. Solaris
Hi,
today when i started the OS Sun Solaris 10 it hangs on initialization. Following was shown in the end of the screen
Initializing system
Please wait....
*
Please help? (3 Replies)
Discussion started by: malikshahid85
3 Replies
8. Solaris
I am running OpenIndiana development version oi_148 32-bit on a seven-year-old Dell Inspiron 8600.
Seems to be running fine except for one particular annoyance: It freezes whenever a system bell/beep plays.
I have mitigated this by turning the system bell off in gnome-terminal, which I use... (3 Replies)
Discussion started by: DeadBadger
3 Replies
9. SCO
SCO Openserver 6.0.0 had an issue with a NIC losing it's config on reboot. Netconfig would not allow "view protocol" and apparently zeroed out the existing IP info. Repaired from console. After this event, however, the system clock seems to lose 30 seconds for every RTC minute that passes. As a... (1 Reply)
Discussion started by: DoublePanic
1 Replies
10. UNIX for Advanced & Expert Users
The book The Design of the Unix Operating System speaks of a clock or timer that is used in scheduling. The clock generates interrupts that update priority information for processes and preempt processes in a round-robin fashion. It's apparent that this "clock" is not the same thing as the CPU... (1 Reply)
Discussion started by: Ultrix
1 Replies
LEARN ABOUT DEBIAN
fake-hwclock
FAKE-HWCLOCK(8) System Manager's Manual FAKE-HWCLOCK(8)
NAME
fake-hwclock - Control fake hardware clock
SYNOPSIS
fake-hwclock [ command ] [ force ]
BACKGROUND
Many embedded Linux systems do not have a functional hardware clock. Either they simply don't have a hardware clock at all or they have a
hardware clock but it is not usable (e.g. because Linux doesn't know how to use it or because no battery is present).
This can lead to time moving backwards to some default value (often 1970) when the system is rebooted. Since lots of software assumes that
time only moves forward this is a bad thing. NTP can (and should where practical) be used to sync with an external timeserver but it is not
available early in the boot process and may be unavailable for other reasons.
DESCRIPTION
fake-hwclock sets and queries a fake "hardware clock" which stores the time in a file. This program may be run by the system administrator
directly but is typically run by init (to load the time on startup and save it on shutdown) and cron (to save the time hourly).
If no command is given then fake-hwclock acts as if the save command was used.
COMMANDS
save Save the time to the file.
load Load the time from the file. If force is specified fake-hwclock will move the clock either backwards or forwards. Otherwise it will
only move it forwards.
FILES
/etc/fake-hwclock.data
The file used to store the time
/etc/init.d/fake-hwclock
The init script used to run fake-hwclock on startup and shutdown
/etc/default/fake-hwclock
Settings file for the init script.
/etc/cron.hourly/fake-hwclock
Cron job used to save the time hourly
ENVIRONMENT VARIABLES
FILE set the file used by fake-hwclock
RETURN VALUES
1 is returned for invalid commands. 0 is returned in all other cases.
BUGS
This approach can only provide a crude approximation of what a real hardware clock provides. Use of NTP or another method to keep the time
in sync is strongly advised.
Debian 5 April 2012 FAKE-HWCLOCK(8)