Sponsored Content
Top Forums Programming setitimer expires in wrong time Post 76417 by inna on Tuesday 28th of June 2005 08:47:58 AM
Old 06-28-2005
Data setitimer expires in wrong time

I set a timer using setitimer to expire every 30 ms.
Usually it does. But sometimes it takes ~ 700 ms between 2 successive arousals (expirations). The timing is crucial for me.

The process with the timer is almost the only one running on the computer.

How do I overcome this problem?
 

9 More Discussions You Might Find Interesting

1. Solaris

cronjob dies when user password expires

I noticed for some time now on solaris 8 whenever our root or oracle password expires after 12 weeks the cronjob for the expired user will totally stop working, it will start working again once the password has been changed. I wonder if anybody encountered this problem and knows of a fix other... (4 Replies)
Discussion started by: sparcguy
4 Replies

2. UNIX for Dummies Questions & Answers

Change Account to not lock account if password expires

I have access to 15+ UNIX boxes at work, and I do not consistently log onto all of them over time. When I do try to access one I havent been on in awhile, my account is locked as the password has expired. I need to request to the UNIX SA's that the password expiration is 90 days and that if it... (1 Reply)
Discussion started by: stringzz
1 Replies

3. Solaris

Check when password expires

How do I check to see when a password expires on a user account with using the CLI? (1 Reply)
Discussion started by: jastanle84
1 Replies

4. UNIX for Dummies Questions & Answers

Wrong Time on Server

Hello Folks, The following: I got to solve a problem for a colleague. I do have an server HP-UX in a network. There is a Time Server, but it has to be adapted, due to NTP not reachable. The time on the server notifies more then 10 minutes in the future. There is a working database on the... (2 Replies)
Discussion started by: velde_van_der_a
2 Replies

5. Shell Programming and Scripting

Create account that expires in 3 days

I was hoping that somebody could help me out with this. I just deployed a new FTP server and I have a script that creates the new account. How would I go about having it expire 3 days after after creation? useradd -s /bin/false -m -p $pass $username (7 Replies)
Discussion started by: binary-ninja
7 Replies

6. UNIX for Dummies Questions & Answers

Cron job executed at wrong time

Dear *nix users. I'm on Mac OS 10.6 / Terminal and try to use crontab to schedule two scripts every 30 minutes and every 41 minutes. I followed the man instructions and created / installed a crontab file for the current user:crontab -e with the following content */30 * * * *... (4 Replies)
Discussion started by: moxnos
4 Replies

7. Shell Programming and Scripting

Why result is wrong here ? whether break statement is wrong ?

Hi ! all I am just trying to check range in my datafile pls tell me why its resulting wrong admin@IEEE:~/Desktop$ cat test.txt 0 28.4 5 28.4 10 28.4 15 28.5 20 28.5 25 28.6 30 28.6 35 28.7 40 28.7 45 28.7 50 28.8 55 28.8 60 28.8 65 28.1... (2 Replies)
Discussion started by: Akshay Hegde
2 Replies

8. Solaris

Wrong time zone for non root user

I have a Solaris-11 zone, which is newely build. Since I am in PST time zone, so I set it with this command. It shows me date correctly with correct time zone, but when I switch it to a non root user and run below java command, it is not showing correct time zone. Not sure, how to set it.... (2 Replies)
Discussion started by: solaris_1977
2 Replies

9. UNIX for Dummies Questions & Answers

VxWorks RTC time giving wrong value at random times

I am seeing a scenario where in if the TIMEZONE environment variable value is set to nothing i.e. putenv "TIMEZONE=" the hardware clock is +1 to software clock.Pasted below the results displayed: -> envShow (global environment) 0: TSC_TIME_FROM_RESET=420150.971529 seconds 1:... (0 Replies)
Discussion started by: snehavb
0 Replies
GETITIMER(2)						      BSD System Calls Manual						      GETITIMER(2)

NAME
getitimer, setitimer -- get/set value of interval timer LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/time.h> #define ITIMER_REAL 0 #define ITIMER_VIRTUAL 1 #define ITIMER_PROF 2 int getitimer(int which, struct itimerval *value); int setitimer(int which, const struct itimerval *value, struct itimerval *ovalue); DESCRIPTION
The system provides each process with three interval timers, defined in <sys/time.h>. The getitimer() system call returns the current value for the timer specified in which in the structure at value. The setitimer() system call sets a timer to the specified value (returning the previous value of the timer if ovalue is not a null pointer). A timer value is defined by the itimerval structure: struct itimerval { struct timeval it_interval; /* timer interval */ struct timeval it_value; /* current value */ }; If it_value is non-zero, it indicates the time to the next timer expiration. If it_interval is non-zero, it specifies a value to be used in reloading it_value when the timer expires. Setting it_value to 0 disables a timer, regardless of the value of it_interval. Setting it_interval to 0 causes a timer to be disabled after its next expiration (assuming it_value is non-zero). Time values smaller than the resolution of the system clock are rounded up to this resolution (typically 10 milliseconds). The ITIMER_REAL timer decrements in real time. A SIGALRM signal is delivered when this timer expires. The ITIMER_VIRTUAL timer decrements in process virtual time. It runs only when the process is executing. A SIGVTALRM signal is delivered when it expires. The ITIMER_PROF timer decrements both in process virtual time and when the system is running on behalf of the process. It is designed to be used by interpreters in statistically profiling the execution of interpreted programs. Each time the ITIMER_PROF timer expires, the SIGPROF signal is delivered. Because this signal may interrupt in-progress system calls, programs using this timer must be prepared to restart interrupted system calls. The maximum number of seconds allowed for it_interval and it_value in setitimer() is 100000000. NOTES
Three macros for manipulating time values are defined in <sys/time.h>. The timerclear() macro sets a time value to zero, timerisset() tests if a time value is non-zero, and timercmp() compares two time values. RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS
The getitimer() and setitimer() system calls will fail if: [EFAULT] The value argument specified a bad address. [EINVAL] The value argument specified a time that was too large to be handled. SEE ALSO
gettimeofday(2), select(2), sigaction(2), clocks(7) HISTORY
The getitimer() system call appeared in 4.2BSD. BSD
May 16, 1995 BSD
All times are GMT -4. The time now is 06:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy