I'm using "trading systems" as an example
unfortunately, even the gethostbyaddr_r series of c functions can hang as well. depending on the load of the box and a dozen other reasons, the response from the name server (or whatever else) may not actually be received.
If a signal comes in and perl core dumps with half finished work... that's fine, there are clean up routines that identify where the breakage occurred and repair whatever was broken.
Using unsafe signals IS okay, IF the proper precautions are taken for recovery and continuing where it broke.
What I'm saying is that unsafe signals do have their uses and should never be removed from perl entirely.. Perhaps perl should be fixed to handle them better?
In reply to Re: Re: Re: Re: Re: Re: Re: Upgrading Perl in production environment
by jfroebe
in thread Upgrading Perl in production environment
by Sprad
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |