First of all, what you are asking is not something I condone nor encourage. It is on a par with removing the battery from the smoke-alarm because it 'false positives' to much when you are cooking bacon. Don't disable the alarm, fix the ventilation on the kitchen!
There is the concept of "Defensive Programming" that you really need to think about here. Why are your scripts cratering? What can you do to code around those conditions? Why aren't you?! Shooting the Messenger is very short sighted....
That said, If it were I in this pickle, I'd start by analyzing the kinds of 'Perl crashes' that cause the flower-box to appear and see if there is a common thread that I can check for. Ideally, you will discover something that you can set a %SIG trap for, and bail out gracefully once you receive the signal. This will require changes in the scripts you are running under the service.
A more heavy weight solution is to install a Monitor Program (I am very fond of Nagios) and have it check your problem-children's metrics (say CPU time consumed, memory foot-print, and log-file size). If the appropriate metric stabilizes for too long (and that's a judgment decision you have to make), have the Monitor kill() the process.
I really can't over-emphasize how dumb/dangerous the idea of disabling the pop-up on crash is.
Consider the following scenario (names changed for obvious reasons):
- The SysOP: Jon, According to my logs, your fizbit program crashed and restarted itself last night; once every five minutes starting at 0035 until I got here at 0800.
- Jon Q. Programmer: Oh? I was getting a lot of errors from it last week, but I fixed that.
- SysOP: Oh, really? and how did you do that?
- JQP: Simple, I redirected the logs to /dev/null
- SysOP: So what happened last night?
- JQP: I don't know, I'll have to check the logs and get back to you. By the way, where is my fizbit Report? Shouldn't it be printed by now?
- SysOP: ....
----
I Go Back to Sleep, Now.
OGB
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.