| … | |
… | |
| 1754 | watchers, as the management overhead dominates. |
1754 | watchers, as the management overhead dominates. |
| 1755 | |
1755 | |
| 1756 | =back |
1756 | =back |
| 1757 | |
1757 | |
| 1758 | |
1758 | |
|
|
1759 | =head1 SIGNALS |
|
|
1760 | |
|
|
1761 | AnyEvent currently installs handlers for these signals: |
|
|
1762 | |
|
|
1763 | =over 4 |
|
|
1764 | |
|
|
1765 | =item SIGCHLD |
|
|
1766 | |
|
|
1767 | A handler for C<SIGCHLD> is installed by AnyEvent's child watcher |
|
|
1768 | emulation for event loops that do not support them natively. Also, some |
|
|
1769 | event loops install a similar handler. |
|
|
1770 | |
|
|
1771 | =item SIGPIPE |
|
|
1772 | |
|
|
1773 | A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef> |
|
|
1774 | when AnyEvent gets loaded. |
|
|
1775 | |
|
|
1776 | The rationale for this is that AnyEvent users usually do not really depend |
|
|
1777 | on SIGPIPE delivery (which is purely an optimisation for shell use, or |
|
|
1778 | badly-written programs), but C<SIGPIPE> can cause spurious and rare |
|
|
1779 | program exits as a lot of people do not expect C<SIGPIPE> when writing to |
|
|
1780 | some random socket. |
|
|
1781 | |
|
|
1782 | The rationale for installing a no-op handler as opposed to ignoring it is |
|
|
1783 | that this way, the handler will be restored to defaults on exec. |
|
|
1784 | |
|
|
1785 | Feel free to install your own handler, or reset it to defaults. |
|
|
1786 | |
|
|
1787 | =back |
|
|
1788 | |
|
|
1789 | =cut |
|
|
1790 | |
|
|
1791 | $SIG{PIPE} = sub { } |
|
|
1792 | unless defined $SIG{PIPE}; |
|
|
1793 | |
|
|
1794 | |
| 1759 | =head1 FORK |
1795 | =head1 FORK |
| 1760 | |
1796 | |
| 1761 | Most event libraries are not fork-safe. The ones who are usually are |
1797 | Most event libraries are not fork-safe. The ones who are usually are |
| 1762 | because they rely on inefficient but fork-safe C<select> or C<poll> |
1798 | because they rely on inefficient but fork-safe C<select> or C<poll> |
| 1763 | calls. Only L<EV> is fully fork-aware. |
1799 | calls. Only L<EV> is fully fork-aware. |
