12-08-2012
It would help if you provide some factual data like what OS you are using, how long does the task is asked to wait and how long does it actually does it.
I any case, on a POSIX compliant system, the clock_nanosleep call might last more than expected because the delay might be rounded up or the system might bee busy doing something else. It shouldn't be shorter unless your process is interrupted by something else.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello every body
goal: create a script that control periodicly ( every 30 min ) if a process is already actif.
How can I do that?
thanks (3 Replies)
Discussion started by: hoang
3 Replies
2. Shell Programming and Scripting
Hello All,
My first post on this forum. I am using cygwin to help me with some routine jobs on my laptop, with tcsh as my shell. I need to copy a set of files from one directory to a network drive every minute. So I have
set tperiod = 1
alias periodic 'cp *.txt /cygdrive/z/Data'
... (0 Replies)
Discussion started by: OmniVision
0 Replies
3. Cybersecurity
I need to periodically run a check on the passwords of the users (Redhat 5.0) to verify that all passwords meet minimal standards. I remember seeing a script years ago that grabbed the encrypted passwords from the file and checked if they matched any of the encrypted strings in another file, plus... (1 Reply)
Discussion started by: tlynnch
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have a file that looks like this, the unity of information is composed of four lines, and these extends for millions.
My objective is to remove the highligthed "T".
How to attack this? This character is always constant in type "T" and position "1st" but the rest of the line is... (7 Replies)
Discussion started by: sargotrons
7 Replies
5. Ubuntu
Ubuntu wireless has been fine until fresh installation of 12.10. Now, I have periodic drops of the wireless. I can manually disconnect and then reconnect to get the service back.
Sometimes, I am unable to disconnect. When this happens, I have to log off and then on again. (0 Replies)
Discussion started by: jamarsh
0 Replies
6. Shell Programming and Scripting
SOLVED, thank you!
Edit2:
Good news everyone,
I managed to get it down to a "simple" problem, but I still have some syntax issues.
Here is the code which troubles me:
awk 'BEGIN{x2=0;x1=0;crit=0;}
$1 < 1000000 {x2=$4; diffx=x2-x1; x1=x2;
diffx > 3.6 ? {crit=1} : {crit=0};... (2 Replies)
Discussion started by: Consti
2 Replies
7. What is on Your Mind?
Was working on Vue.js and stumbled upon this beautiful Vue project by Kadin Zhang
Periodicity is a dynamic periodic table built with Vue.js that animates and graphs data to aid the visualization of chemical concepts.
The code is available on GitHub (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT POSIX
drv_usecwait
drv_usecwait(9F) Kernel Functions for Drivers drv_usecwait(9F)
NAME
drv_usecwait - busy-wait for specified interval
SYNOPSIS
#include <sys/types.h>
#include <sys/ddi.h>
void drv_usecwait(clock_t microsecs);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI).
PARAMETERS
microsecs The number of microseconds to busy-wait.
DESCRIPTION
drv_usecwait() gives drivers a means of busy-waiting for a specified microsecond count. The amount of time spent busy-waiting may be
greater than the microsecond count but will minimally be the number of microseconds specified.
delay(9F) can be used by a driver to delay for a specified number of system ticks, but it has two limitations. First, the granularity of
the wait time is limited to one clock tick, which may be more time than is needed for the delay. Second, delay(9F) may only be invoked
from user context and hence cannot be used at interrupt time or system initialization.
Often, drivers need to delay for only a few microseconds, waiting for a write to a device register to be picked up by the device. In this
case, even in user context, delay(9F) produces too long a wait period.
CONTEXT
drv_usecwait() can be called from user or interrupt context.
SEE ALSO
delay(9F), timeout(9F), untimeout(9F)
Writing Device Drivers
NOTES
The driver wastes processor time by making this call since drv_usecwait() does not block but simply busy-waits. The driver should only make
calls to drv_usecwait() as needed, and only for as much time as needed. drv_usecwait() does not mask out interrupts.
SunOS 5.10 12 Nov 1992 drv_usecwait(9F)