In the spirit of TMOTOWTDI, you could, in your perl script have whatever you are trying to do be done within the context of a signal handler. For example, #!/bin/perl
$SIG{INT} = \&my_sub;
sub my_sub
{
$SIG{INT} = \&my_sub;
#do stuff
}
while (1)
{
#waiting for my signal...
}
Then, put an entry in the crontab to send your process a SIGINT every minute ( kill -INT (your pid here)). You may even be able to put the entry in the crontab through the script (I would try to figure it out myself, but I'm a bit sleepy right now). So, now with the signal handler installed, your script will "do stuff" only when it catches a <code>SIGINT<code>, which you've aranged to be once a minute. You also get the benefit of having your process be persistent, so that the loading of it into memory isn't an issue if it ever was to begin with. thor
-
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.
|