Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
The halt script indeeds clarifies this question. First a TERM signal and after 5 seconds a KILL signal.

  • Why not having the cleanup code in the signal handler itself, though?

    It also needs to execute when the programs ends normally, so the END block is probably the best place.

  • Why don't you try to detect and delete the stale database record at startup if possible?

    Since I store the PID value of the process in a database, this PID might be re-used by the operating system when deleting the record at startup.
    Thanks for your helpful input.

    In reply to Re^2: Signals and END block by Marcello
    in thread 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.