… | |
… | |
378 | |
378 | |
379 | AnyEvent also has some other, more esoteric event sources you can tap |
379 | AnyEvent also has some other, more esoteric event sources you can tap |
380 | into: signal and child watchers. |
380 | into: signal and child watchers. |
381 | |
381 | |
382 | Signal watchers can be used to wait for "signal events", which simply |
382 | Signal watchers can be used to wait for "signal events", which simply |
383 | means your process got send a signal (Such as C<SIGTERM> or C<SIGUSR1>). |
383 | means your process got send a signal (such as C<SIGTERM> or C<SIGUSR1>). |
384 | |
384 | |
385 | Process watchers wait for a child process to exit. They are useful when |
385 | Process watchers wait for a child process to exit. They are useful when |
386 | you fork a separate process and ened to know when it exits, but you do not |
386 | you fork a separate process and ened to know when it exits, but you do not |
387 | wait for that by blocking. |
387 | wait for that by blocking. |
388 | |
388 | |