DragonFly kernel List (threaded) for 2003-07
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
userapi: signals
Any thought of how signals will be handled once there's nothing but
messages? For most cases, they could be done in the user API when you
Wait() on the system message port, but that won't stop a program that's
in an infinite (or just very long) loop.
The easy solution would be to have a background thread that was always
live that just handled signals, either by sleeping on a port or by being
the interrupt handling thread for that process, no?
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]