Has anyone used DateTime::Event::Cron?

It looks useful but I got hung up immediately on some basics. This code should, I think, show me each crontab entry, then show me just the command:
use strict; use DateTime::Event::Cron; my @entries = DateTime::Event::Cron->new_from_crontab (file => '/tmp/crontab.out'); my $entry; foreach $entry (@entries) { print $entry->original(), "\n"; print " ", $entry->command(), "\n"; }
The full entry prints fine, but the commands are all missing the leading token of the command (the program name) -- only the command arguments are shown. I believe all of the commands are full paths and therefore contain forward slashes. Some of the docs. point to an expanded cron syntax that supports slashes, so I'm wondering if maybe that has something to do with it.

At any rate, I'd be interested to hear other monks' experience with this module.


In reply to DateTime::Event::Cron by steves

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.