In a POSIX environment, causing a long-running process such as a daemon to stop and load the latest configuration information is often associated with the HUP signal.
Perhaps you could put in a signal handler that would allow you to eval some new code in, and then continue, along the following (untested) lines:
my $code_file = '/tmp/myscript.cmds';
$SIG{HUP} = sub {
unless ( -e $code_file ) {
warn "Received HUP signal, but no command file.";
return;
}
eval {
require $code_file;
unlink $code_file;
};
if ( ! $@ ) {
warn "Caught HUP signal and processed command file";
} else {
warn "Caught HUP signal but unable to process commands: $@";
}
};
While your script is running interactively, you can use another session to write commands to this file and HUP your running Perl process.
> echo "$foo = 27" >> /tmp/myscript.cmds
> killall -HUP perl
A major caveat: signal handlers are notoriously finicky and idiosyncratic, so this approach might not be particularly reliable or portable.
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.