Whenever I upgrade running processes, I check lsof. Specifically, lsof | grep DEL.*lib | less -S (as root). Any process there (the first column) needs to be considered for restarting at your earliest opportunity. Generally, this includes a lot of my desktop apps which I worry about less, since I just log out and log back in and they'll all be reloaded (sometimes, this includes kwin, or even X, which pretty much necessitates this approach). Others are simply a restart of their file in /etc/init.d.

This applies to all processes, not just perl. It just so happens that it will probably solve your perl question, too, as the perl executable is one of the open files that will be missing.

In reply to Re: graceful handling of perl upgrades on server? by Tanktalus
in thread graceful handling of perl upgrades on server? by bcrowell2

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.