Jira (PUP-1280) windows agents don't parse runinterval as a duration setting

[Nicholas Fagerlund (JIRA)]

Title: Message Title

Nicholas Fagerlund commented on an issue   Re: windows agents don't parse runinterval as a duration setting I just experimented a bunch, and the %x{ command } ...syntax appears to simply not work at all on Windows for any purpose whatsoever. At least in this script. I added some debug lines to daemon.rb: # runinterval_source = %x{ "#{puppet}" agent --configprint runinterval } runinterval_source = %x{ echo "hi" } log_err("detected runinterval is #{runinterval_source}") runinterval = runinterval_source.to_i It always logs "detected runinterval is " with no value, no matter what I put in the %x brackets. The execute statement must be returning nil. That's why changing the runinterval has no effect. What would be another way to execute commands and get their output? And why is %x not working like normal, here? Add Comment   Puppet / PUP-1280 windows agents don't parse runinterval as a duration setting When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds. In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc <http://docs.puppetlabs.com/references/latest/configuration.html... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.