And to argue the other way (somewhat), for a grainyness of one minute you well may be better off with a persistent program. How much startup overhead there is to your program sould influence your decision. If it's a 100 line program that just diddles a logfile or three, you'll probably be better off running from cron. If it's a 10's-of-thousand line monster that has to do 45 seconds of initialization before it runs and generates gobs of network traffic at startup, consider a persistent daemon.

If you do make it persistent, consider POE which will give you an easy way to setup getting poked at the right interval (c.f. POE::Kernel's delay_add method).

In reply to Re: writing looped programs by Fletch
in thread writing looped programs by tachekent

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.