Yeah, that looks feasible in general, but as I mentioned in my OP, I don't want it to exit/die ever.
(Thx for looking that up for me anyway)
All the variations I've tried so far enable you to trap an error and do some(!) extra processing, then die/exit.
The prob I'm getting is that if you want to continue anyway, which I do, it's pretty consistent (see my results) that after approx 3 DB related errors, Perl dies regardless, even if you use a SIG{__DIE_} trap! :-(
If you know how to do what I want, I'll owe you big time...
Don't suppose you know how I could get someone like Merlyn or some other Perl internals guy to look at this? I feel it ought to be possible.
As background, the system is setup such that MySQL will (eventually) re-start, but I want my progs to survive till then, not die/restart as well.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.