Hi,

My Perl server runs 24/7. Whenever the program is stopped, it needs to delete the database record it created on startup so everything is in sync. This is done in the END block. This line will make sure the END block is executed whenever such a signal is received (I know, I could also 'IGNORE' them):

$SIG{TERM} = $SIG{INT} = $SIG{QUIT} = $SIG{HUP} = sub { die; };
[download]

Questions:

What signal is sent to a process when the machine is restarted (KILL?)

Does the KILL signal cause the END block to be executed (since it cannot be caught)?

Is it 100% sure the END block is executed using the above code or might there be other situations in which this fails?

I'm trying to prevent my server from exiting without execution of the END block.

Thanks for any input

Update: I'm on Redhat Linux

---

In reply to Signals and END block by Marcello

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.