>>>>> "BT" == Bennett Todd <[EMAIL PROTECTED]> writes:
BT> How about, goosing long-lived daemons to ask 'em to re-read their
BT> config files? The only signal code I ever wrote for perl was for
BT> that --- and never did manage to work my way around to testing the
BT> resulting code enough to convince myself it was really correct, so I
BT> never did deploy it. My sighandler just modified the value of a "use
BT> vars" package-scope scalar flag, which was then checked and dealt
BT> with in the main processing loop, right before it'd try to actually
BT> do anything. Is that code pattern safe now? If not, can we design to
BT> guarantee that it is?
there are plenty of uses for signals beyond the popular SIGHUP to a
server. you don't see many useful signal things in perl since they are
known to be broken. what about SIGCHLD to manage and reap child
processes, SIGINT to handle keyboard ^C, etc?
read my rfc on safe signals. there are clean ways to handle them but
they have to be integrated with the various subsystems dan is writing
about.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
