Printable View
Hello!
I'm writing a program that have to write every 1.654 seconds (this number is random). The real time I have to wait is calculated and safe in a double type variable. Does anybody know how to make it? I've tried with nanosleep and usleep. But when I try to handle the time variables all goes crazy! Thank for your help.
"the time variables all goes crazy" means what?
So I presume you are doing this in Linux.
You are, I presume, aware that Linux is not a real-time OS, and thus makes no express or implied warranty with regards to it's "timeliness" - usleep and nanosleep are both capable of sleeping for a set amount of time, but it's a "best effort", and although the names imply that they are micro or nanosecond precise, they are not guaranteed to be very precise [how good or bad they are will depend partly on what hardware you are doing this on].
The other thing I'm not clear on is your statement "has to write every X seconds" - what are yout "writing" and where is that write intended for? If it's a write to for example disk or network, there's absolutely no guarantee that it will actually get done any time real soon after you issuing the write from your application. Obviously a write to a hardware register will be much more direct.
It may be easier to explain what you may need to do or what you can't do if you post a small example of what you're trying to do...
--
Mats
Most implementations of sleep/delay/whatever only guarantee a MINIMUM time, that is AT LEAST the amount you request for.
Asking to sleep for 1 second, but coming back 20 seconds later is within spec (maybe that is not what you want).
Unless you're programming on a machine where you have absolute control over everything (a standard desktop machine with any popular OS doesn't count), getting absolute timings is going to be tricky at best.
I'll try to explain better. Sorry.
I want to make a program that every 0.5 secs makes a printf("It has passed 0.5 sec"). I don't mind if the precision isn't very good.
The problem with the time variables is that I don't know wich values gives to a variable that is of time_t for example.
I think of using a solution like these one:
Code:
int time_sec;
int time_usec;
time_sec = 0;
time_usec = 500000;
while(TRUE){
sleep(time_sec);
usleep(time_usec);
printf("It has passed %f sec\n",time_sec+time_usec*1e-6);
}
Not sure what you mean you want to do with time_t, and how that relates to your code.
usleep and sleep are both (generally) implemented as calls to nanosleep with a suitably multiplied input amount of time. (e.g. usleep is essentially nanosleep(time * 1000) [yes, I know, that's not the right way to call nanosleep].
So calling sleep followed by usleep won't really make much sense.
--
Mats
That one was for McGyver ;) As you say useless in my code.Quote:
Originally Posted by matsp
usleep and sleep are both (generally) implemented as calls to nanosleep with a suitably multiplied input amount of time. (e.g. usleep is essentially nanosleep(time * 1000) [yes, I know, that's not the right way to call nanosleep].
In this case maybe not, but what if you want to make a 1.25 second sleep? usleep uses usecond_t variables. And the type useconds_t is an unsigned integral capable of storing values at least in the range zero to 1,000,000 that's from 0 to 1 sec I think.Quote:
Originally Posted by matsp
--
Mats[/QUOTE]
The sleep() family of functions have nothing to do with time_t.
So....
What is the issue again?
If you want to sleep 1.25 seconds, you specify 1250000 ((int)(1.25 * 1e6) if you want it as a calculation, or 1250 * 1000 for integer, where 1250 is the number of milliseconds you want to sleep) to usleep. useconds_t is certainly a 32-bit integer if it's not larger, so you should be fine up to about 2000 seconds at least.
--
Mats
[/QUOTE]Quote:
Originally Posted by bartleby84
If you wanted a 1.25 second sleep, you'd call sleep with 1250 as an argument, clearly.. One second = 1000 milliseconds.
If you wanted a 1.25 second sleep, you'd call sleep with 1250 as an argument, clearly.. One second = 1000 milliseconds.[/QUOTE]
usleep takes a number of microseconds, so passing it that type of value is probably best, hence my suggestion of using milliseconds * 1000.
sleep (in Linux) sleeps for a number of seconds.
Both are different from Sleep in Windows and delay in Borland/TurboC that uses millieseconds as their inputs.
--
Mats
I first tried to use the nanoleep() function that need a timespec struture and this structure has two variables, one is a long to represent the nanosecs (from 0 to 1 sec) an the other one to represent the secs is a time_t variable.Quote:
Originally Posted by MacGyver
Thats is new for me I read from http://www.opengroup.org/onlinepubs/...s/types.h.html that useconds_t has a limited range. There was my problem.Quote:
Originally Posted by matsp
From your source:
I strongly doubt that it would not support a value of 1,250,000 on your architecture, but whatever.Quote:
The type useconds_t shall be an unsigned integer type capable of storing values at least in the range [0, 1000000].
I tried to make a usleep(2000000) and it works.
Yes, I'm quite convinced that it will be fine to do (noticably) longer than that too. The only basic type that holds more than 1 million is a 32-bit integer, so there's no point in artficially restricting to below that . Try sleeping for 20 or 200 seconds and see if that works, just for the fun of it (why not write a little application that takes a number of milliseconds to sleep, and try a few different things out).
--
Mats