Timeline for Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2012 at 5:10 | comment | added | tylerl | @porg you need to use date +%S.%N to get the number of seconds with sub-second precision, and usleep to sleep with sub-second precision, but after that it's just a matter of math. | |
| Jul 23, 2012 at 23:13 | comment | added | porg | I guess you meant the same like @lynxlynxlynx | |
| Jul 23, 2012 at 22:39 | comment | added | porg | @tylerl: How would the concrete command line look like for your solution? | |
| Jul 17, 2012 at 16:24 | comment | added | tylerl | Whether or not you block, the mechanism works just fine. If you block, you sleep the time left after blocking. If you dont block, then your timing thread or process is sleeping while the other is working. Either way, same result. | |
| Jul 17, 2012 at 9:37 | comment | added | symcbean | I think it's also very probable that the programs porg has tested block while running the intended process - which logically they should do to avoid killing the machine they are running on. | |
| Jul 16, 2012 at 21:34 | history | answered | tylerl | CC BY-SA 3.0 |