|
Hi Aaron,
If my calcs are correct, and based on the following url, 300000 microseconds should equal 3 seconds which is NOT what my joblog is conveying. http://www.sengpielaudio.com/calculator-millisecond.htm
A microsecond is one millionth of a second. (That site agrees.) You only specified 300,000 microseconds, which is only 0.3 seconds (as Joe pointed out.)
When you add the time it takes to do the DSPLY and other opcodes, and other things happening on the system, I'd say your delay is accurate (or at least as close as it can be on a multi-user system)
You might be tempted to think that you could add a zero and specify 3,000,000 microseconds (or 3 seconds) to the usleep() API. However, usleep() doesn't work with numbers that large. If you want to sleep for an entire second (or longer) you should use the sleep() API instead.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
