Linux coreutils timeout Relative or Absolute time? -


I am using coreutils 8.13 and want to use a timeout command to combine it with a dragon subproses. If the system clock is changed during long lasting call, then will the timeout command work? In other words, does the timeout command use absolute timing (affected by changing system clock) or relative time (unused by changing system clock)?

EDIT: After some excavation, I have reduced the answer, depending on the behavior of "alarm" in Unistd.h. Still digging through the source ... Please save me

< P> Editing 2: Old version of Corrects (& lt; 8.13) uses an alarm (2) from time to time with ITMEEL (> = 8.13) timer_create (2) with CLOCK_REALTIME for timeout Use Post tells me that my implementation is on the system clock Though it should be affected by the recitation, it is not. A simple test using a Python script, while running a loop, shows me that changing the system clock does not affect the timeout ???

CLOCK_REALTIME clock adjustments have no effect on the relative timer based on that clock.

At least, according to.


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -