in reply to Parsing 'uptime' output

If you find Zaxo's solution imaginative but complex and are put off by the sight of sauoq's daunting collection of brackets, comma's and star's that are so difficult to understand as well as get right, you might like to try:

Start with your example string

10:03pm up 3 days, 9:27, 1 user, load average: 0.00, 0.00, 0.00

Put brackets around the bits you want to capture:

(10:03pm) (up 3 days, 9:27), (1 user), (load average: 0.00, 0.00, +0.00)

Anchor the ends: (not always strictly necessary, but it usually doesn't hurt).

^(10:03pm) (up 3 days, 9:27), (1 user), (load average: 0.00, 0.00, + 0.00)$

Substitute the minimum necessary for the bits that change:

^(.+?m) (up .+? days, .+?:.+?), (.+? user), (load average: .*?)$

Deal with possible plurals: (Note: the s on users)

^(.+?m) (up .+? days?, .+?:.+?), (.+? users?), (load average: .*?) +$

Wrap in delimiters, bind and assign to the variables of your choice:

($Time, $Uptime $Current_Users,$CPU_Load) = `/usr/bin/uptime` =~ /^(.+?m) (up .+? days?, .+?:.+?), (.+? users? +), (load average: .*?)$/;

Used on your sample input it renders:

($Time, $Uptime, $Current_Users,$CPU_Load) = '10:03pm up 3 days, 9:27, 1 user, load average: 0.00, 0.00, 0. +00' =~ /^(.+?m) (up .+? days?, .+?:.+?), (.+? users?), (load aver +age: .*?)$/; print '[', $Time, '] [', $Uptime, '] [', $Current_Users, '] [', $C +PU_Load, ']'; # Ouput [10:03pm] [up 3 days, 9:27] [1 user] [load average: 0.00, 0.00, 0. +00]

Possibly not as good as the other solutions, but arguably easier to modify if you wanted to adjust it yourself.


What's this about a "crooked mitre"? I'm good at woodwork!

Replies are listed 'Best First'.
Re^2: Parsing 'uptime' output
by Aristotle (Chancellor) on Aug 19, 2002 at 04:22 UTC
    Careful. uptime's output is dependent on how much time has passed. The .+? days bit may not always be there for example. That's why I, in general, would agree with rob_au on getting the information from a more friendly interface - of course, the caveats sauoq mentioned apply here. Choose your poison.

    Makeshifts last the longest.

      Valid point, but as someone's sig. reads: "Teach a man to fish...".

      I did mention that my testing was based upon his sample uptime output. Maybe I should have also said that if the format of the output varies from that (more than the pluralisation of day(s) and user(s)), he will have to read perlre and/or perlretut to work out how to adjust it further.


      What's this about a "crooked mitre"? I'm good at woodwork!