Collaboration diagram for Globus Callback Signal Handling:
![]() |
|
Use this to trap interrupts (SIGINT on unix). In the future, this will also map to handle ctrl-C on win32. |
|
Fire a callback when the specified signal is received. Note that there is a tiny delay between the time this call returns and the signal is actually handled by this library. It is likely that, if the signal was received the instant the call returned, it will be lost (this is normally not an issue, since you would call this in your startup code anyway)
|
|
Unregister a signal handling callback.
|
|
Register a wakeup handler with callback library. This is really only needed in non-threaded builds, but for cross builds should be used everywhere that a callback may sleep for an extended period of time. An example use is for an io poller that sleeps indefinitely on select(). If the callback library receives a signal that it needs to deliver asap, it will call the wakeup handler(s), These wakeup handlers must run as though they were called from a signal handler (don't use any thread utilities). The io poll example will likely write a single byte to a pipe that select() is monitoring. This handler will not be unregistered until the callback library is deactivated (via common).
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org