Re:Most operating systems have implemented realtime signals ...
by pjc50 on Monday November 03, 2014 @11:35AM
(#8551678)
The intended use case is people trying to write realtime systems - that is, systems with a latency guarantee, like antilock brakes or flight control systems - in UNIX.
However, no sensible person would write such a thing in a general-purpose multi-user operating system. Realtime is hard, see the Toyota mess: http://www.viva64.com/en/a/0083/
"Move fast and break things" is not a great motto for automotive control software.
Re:Most operating systems have implemented realtime signals ...
by amelius on Monday November 03, 2014 @03:26PM
(#8553252)
How about games, where, e.g., sound effects have a maximum acceptable delay w.r.t. the physics that generates them?
Re:Most operating systems have implemented realtime signals ...
by justincormack on Monday November 03, 2014 @04:15PM
(#8553566)
Signals are not a great mechanism anyway, it turned out.
Re:Most operating systems have implemented realtime signals ...
by gaius on Monday November 03, 2014 @04:12PM
(#8553543)
Well, any sort of process control too (as in, controlling an assembly line or a chemical plant).
Re:Most operating systems have implemented realtime signals ...
by rzezeski on Monday November 03, 2014 @11:44AM
(#8551749)
According to POSIX.1b RT signals are used for other features defined in .1b. An excerpt from "POSIX.4 Programmers Guide":
> So far, we've talked about real-time signals sent by the sigqueue function. However, most POSIX.4 signals are sent as a result of three other facilities in POSIX.4. We'll cover these facilities in detail in their own chapters, but for now, you need to know that realtime signals can be generated as a result of expiration of a POSIX.4 timer, completion of asynchronous I/O, and by arrival of a message on an empty message queue.
Linux reserves 2-3 RT signals for use in its threading library:
So anyone used real-time signals and why did you pick them instead of something else?