Jira (FACT-658) facter doesn't parse gnu uptime output

[William Hopper (JIRA)]

Title: Message Title

William Hopper commented on FACT-658   Re: facter doesn't parse gnu uptime output I'm actually having trouble getting the original issue to reproduce in either x86 Sol 11.1 or Sol 11.2. In the case where /usr/bin/uptime is used: vagrant@vagrant-solaris:~/facter$ /usr/bin/uptime 5:28pm up 35 min(s), 2 users, load average: 0.00, 0.00, 0.01   vagrant@vagrant-solaris:~/facter$ ruby -I ./lib bin/facter system_uptime DEBUG: COMMAND: /usr/bin/uptime DEBUG: uptime case 6, collected output: 35   {"seconds"=>2100, "hours"=>0, "days"=>0, "uptime"=>"0:35 hours"} ... and the case where /usr/gnu/bin/uptime is used: vagrant@vagrant-solaris:~/facter$ /usr/gnu/bin/uptime 17:30pm up 0:36, 2 users, load average: 0.00, 0.00, 0.01   vagrant@vagrant-solaris:~/facter$ ruby -I ./lib bin/facter system_uptime DEBUG: COMMAND: /usr/gnu/bin/uptime DEBUG: uptime case 4, collected output: 17:30pm up 0:36, 2 users, load average: 0.00, 0.00, 0.01   {"seconds"=>2160, "hours"=>0, "days"=>0, "uptime"=>"0:36 hours"} In both cases, the format of the output is handled by the existing case statement in lib/facter/util/uptime.rb. I see that Rahul was able to reproduce this, but I'm wondering if he did in on a SPARC machine, or if that would make a difference here? Add Comment   This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.