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
time.h(3HEAD) Headers time.h(3HEAD)
NAME
time.h, time - time types
SYNOPSIS
#include <time.h>
DESCRIPTION
The <time.h> header declares the structure tm, which includes the following members:
int tm_sec /* seconds [0,60] */
int tm_min /* minutes [0,59] */
int tm_hour /* hour [0,23] */
int tm_mday /* day of month [1,31] */
int tm_mon /* month of year [0,11] */
int tm_year /* years since 1900 */
int tm_wday /* day of week [0,6] (Sunday =0) */
int tm_yday /* day of year [0,365] */
int tm_isdst /* daylight savings flag */
The value of tm_isdst is positive if Daylight Saving Time is in effect, 0 if Daylight Saving Time is not in effect, and negative if the
information is not available.
The <time.h> header defines the following symbolic names:
NULL
Null pointer constant.
CLOCKS_PER_SEC
A number used to convert the value returned by the clock() function into seconds. See clock(3C).
CLOCK_PROCESS_CPUTIME_ID
The identifier of the CPU-time clock associated with the process making a clock() or timer*() function call.
CLOCK_THREAD_CPUTIME_ID
The identifier of the CPU-time clock associated with the thread making a clock() or timer*() function call.
The <time.h> header declares the timespec structure, which has the following members:
time_t tv_sec /* seconds */
long tv_nsec /* nanoseconds */
The <time.h> header declares the itimerspec structure, which has the following members:
struct timespec it_interval /* timer period */
struct timespec it_value /* timer expiration */
The following manifest constants are defined:
CLOCK_REALTIME The identifier of the system-wide realtime clock.
TIMER_ABSTIME Flag indicating time is absolute. For functions taking timer objects, this refers to the clock associated with the
timer.
CLOCK_MONOTONIC The identifier for the system-wide monotonic clock, which is defined as a clock whose value cannot be set with
clock_settime() and that cannot have backward clock jumps. The maximum possible clock jump is implementation-
defined. See clock_settime(3RT).
The clock_t, size_t, time_t, clockid_t, and timer_t types are defined as described in <sys/types.h>. See types.h(3HEAD).
Although the value of CLOCKS_PER_SEC is required to be 1 million on all standard-conforming systems, it can be variable on other systems,
and it should not be assumed that CLOCKS_PER_SEC is a compile-time constant.
The <time.h> header provides a declaration for getdate_err.
The following are declared as variables:
extern int daylight;
extern long timezone;
extern char *tzname[];
Inclusion of the <time.h> header can make visible all symbols from the <signal.h> header.
USAGE
The range [0,60] for tm_sec allows for the occasional leap second.
tm_year is a signed value; therefore, years before 1900 can be represented.
To obtain the number of clock ticks per second returned by the times() function, applications should call sysconf(_SC_CLK_TCK). See
times(2) and sysconf(3C).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO
time(2), utime(2), clock(3C), ctime(3C), difftime(3C), getdate(3C), mktime(3C), strftime(3C), strptime(3C), types.h(3HEAD), clock_set-
time(3RT), nanosleep(3RT), timer_create(3RT), timer_delete(3RT), timer_settime(3RT), attributes(5), standards(5)
SunOS 5.10 10 Sep 2004 time.h(3HEAD)