Sponsored Content
Top Forums Programming setitimer expires in wrong time Post 76437 by jim mcnamara on Tuesday 28th of June 2005 10:29:35 AM
Old 06-28-2005
You have to elevate the priroity of the process so it has a higher prioity than any of the other processes

see man 2 nice
 

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

NAME
ualarm - schedule signal after specified time SYNOPSIS
unsigned ualarm(value, interval) unsigned value; unsigned interval; DESCRIPTION
This is a simplified interface to setitimer(2). Ualarm causes signal SIGALRM, see signal(3C), to be sent to the invoking process in a number of microseconds given by the value argument. Unless caught or ignored, the signal terminates the process. If the interval argument is non-zero, the SIGALRM signal will be sent to the process every interval microseconds after the timer expires (e.g. after value microseconds have passed). Because of scheduling delays, resumption of execution of when the signal is caught may be delayed an arbitrary amount. The longest speci- fiable delay time (on the vax) is 2147483647 microseconds. The return value is the amount of time previously remaining in the alarm clock. SEE ALSO
getitimer(2), setitimer(2), sigpause(2), sigvec(2), signal(3C), sleep(3), alarm(3), usleep(3) NOTES (PDP-11) On the PDP-11, setitimer(2) rounds the number of microseconds up to seconds resolution, therefore ualarm doesn't give you any more resolu- tion than alarm(3). 4.3 Berkeley Distribution August 26, 1988 UALARM(3)
All times are GMT -4. The time now is 04:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy