Error conditions, other considerations
Posted Sep 28, 2007 22:24 UTC (Fri) by filker0
Parent article: The new timerfd() API
I have not followed this, and my quick tracing of articles didn't lead to answers to a few questions that I have.
- What error is returned if a non-timer fd is used in a call to timerfd_settime() or timerfd_gettime()?
- What error is returned (if any) when a timer fd is passed to close()?
- Are the timer fds unique across the entire system?
- Are timer fds inherited or duplicated across a fork? Exec?
- Are timers destoryed when the process ends?
- Can one process set a timer for another?
If the answer to #6 is "Yes", it would introduce a nice IPC mechanism that I could see being useful in GUI, simulation, and automated test software. Of course, the answer to #6 depends on #s 3 and 4. Also, certain of these would have security implications as well.
I suppose I ought to get a recent kernel source distro, apply the proposed patches, then search out the man page, look at the implementation, and see if I can find any flaws in the API that should be addressed.
to post comments)