Sponsored Content
Top Forums UNIX for Advanced & Expert Users Xt timer call, XtAppAddTimeout, hangs on system clock jump backwards Post 303020499 by altrefrain on Saturday 21st of July 2018 07:48:52 AM
Old 07-21-2018
That's a good question. The system is connected to an ntp server. The user sets their IP address from within the application at which time it connects to the server and the time jump can occur. The time jump isn't happening constantly; just on that initial connection. But, if the time jump is significant, it's a show stopper, where the only remedy is to restart the box/application.
 

10 More Discussions You Might Find Interesting

1. AIX

AIX 5.3 12 Hour System Clock

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

clock() call returning zero always

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

how to differentiate system call from library call

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

ABOUT RECV() SYSTEM CALL (regarding timer)

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

Recv() call with timer(time out )

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

Sync Solaris System Clock With PDC Using Cron

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

System hangs

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

System hangs (freezes) on system bell/beep

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

System Clock running at half speed

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 UNIX clock/timer interrupt

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
PMTIME(3)						     Library Functions Manual							 PMTIME(3)

NAME
pmtime, pmTimeConnect, pmTimeDisconnect, pmTimeRecv, pmTimeSendAck, pmTimeShowDialog - time control functions for synchronizing the archive position and update interval between one or more applications C SYNOPSIS
#include <pcp/pmtime.h> int pmTimeConnect(int port, pmTime *state); int pmTimeDisconnect(int fd); int pmTimeSendAck(int fd, struct timeval *fetchTime); int pmTimeShowDialog(int fd, int show); int pmTimeRecv(int fd, pmTime *state); cc ... -lpcp_gui DESCRIPTION
These functions form part of the Performance Metrics Applications Programming Interface (PMAPI) and are intended to provide a uniform mech- anism for applications to both replay archive data and report live data in a time synchronized manner. The pmTime structure has the following fields: typedef struct { unsigned int magic; unsigned int length; pm_tctl_command command; pm_tctl_source source; pm_tctl_state state; pm_tctl_mode mode; struct timeval delta; struct timeval position; struct timeval start; /* archive only */ struct timeval end; /* archive only */ char data[0]; /* arbitrary length info (TZ) */ } pmTime; In the simplest case, the application should call pmTimeConnect to connect to the time control server, pmtime(1), and then repeatedly call pmTimeRecv in the main loop of the application. On success, pmTimeConnect returns a non-negative file descriptor. In applications which have multiple threads of control, rather than simply blocking in pmTimeRecv, the file descriptor may be used in calls to select(2). In graphical applications, the file descriptor may be used to interface with the event loop. The port parameter to pmTimeConnect is the port number of the socket on which the time control server is (or will be) listening for new connections. The state parameter to pmTimeConnect is used to initialize a new time control server or to pass additional information to an existing time control server. The start and finish fields indicate the chronological bounds interesting to the application. The showdialog field indi- cates whether the time control server should initially show or hide the dialog. The position, delta, and data fields indicate the initial archive position, update interval, time zone string and time zone label string. pmTimeRecv blocks until the time control server sends a command message. It then updates the state parameter and returns one of the PM_TCTL command identifiers. The PM_TCTL_SET command indicates the application should seek to the archive position (see pmSetMode(3)) returned in the position field of the state parameter. The PM_TCTL_STEP command indicates the application should perform an update, i.e. advance (or rewind, if delta is negative) to the time indicated by position and then fetch new metric values, update the display or whatever. In order for several application to remain syn- chronized, the time control server will wait until all applications have acknowledged that they have completed the step command. Applica- tions should call pmTimeSendAck when the step command has been processed. Note that PM_TCTL_STEP is the only command that requires an explicit acknowledgement. The PM_TCTL_VCRMODE command is used by the time control server to indicate the current VCR mode. The value is returned in the vcrmode field of the state parameter passed to pmTimeRecv, and remains valid until the next PM_TCTL_VCRMODE command is received. The PM_TCTL_TZ command indicates the application should use a new time- zone, as indicated in the tz and tzlabel fields of the state param- eter. The PM_TCTL_BOUNDS command is sent to all applications when the time control server changes its chronological bounds. This may occur when a new application connects to the time control server or the user changes the bounds manually. Most applications will ignore this command. The PM_TCTL_SHOWDIALOG command will be sent to all applications when the visibility of the time control server changes. This allows appli- cations to alter the text in menus or buttons to reflect this change. Applications may change the visibility of the time control dialog using the pmTimeShowDialog function. The initial visibility is determined when the time control dialog is first created by an application calling pmTimeConnect with the showdialog field in the state parameter set to the desired value. The pmTimeDisconnect function may be used to close the command socket to the time control server. This is useful when applications need to change the connection mode, e.g. to divorce the current time control server and connect to a new one. SEE ALSO
pmtime(1), PMAPI(3) and pmSetMode(3). Performance Co-Pilot Aconex PMTIME(3)
All times are GMT -4. The time now is 11:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy