Another way which may prove to be other a better alternative is to read the uptime directly from /proc/uptime (assuming that this interface is available to you) - This allows for vagarities of uptime output and regular pattern matching to sidestepped altogether.

For example:

use Date::Calc qw/ Normalize_DHMS /;
use IO::File;

#   get_uptime function - returns uptime from /proc/uptime
#   as 4-member array representing current system uptime in
#   days, hours, minutes and seconds

sub get_uptime {
    my $uptime;
    my $fh = IO::File->new('/proc/uptime', 'r');
    $uptime = (split /\s+/, <$fh>)[0] if defined $fh;
    return Normalize_DHMS(0, 0, 0, $uptime) if defined $uptime;
}

[download]

 

In reply to Re: pattern matching by rob_au
in thread pattern matching by Anonymous Monk

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.