You haven't given enough details to be sure, but it sounds like you're running under mod_perl. mod_perl makes a persistent Perl interpreter per child httpd process and things get loaded once (more or less) at child start time. Then again that's why you use it (in production you bypass all that startup overhead after the first request).

There are things like Apache::StatINC (but that's for mod_perl 1; I can't recall what the mp2 one is called) for making changes visible immediately at the cost of a few more system calls each request; that may be what you're interested in. Alternately if you're writing a CGI that's eventually going to run under Apache::Registry (or whatever the mp2 analogue is), configure things to run it as a real run-and-exit CGi during development and testing.

In reply to Re: Module updates require webserver restart? by Fletch
in thread Module updates require webserver restart? by Calm

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.