On Wed, Oct 30, 2013 at 6:06 PM, Glenn Sarti <[email protected]> wrote:
> * A side effect of not running the daemon from a CMD.EXE was that the >> call to get to runinterval was failing. I suspect this is due to STDOUT >> not being available anymore. So I used the well worn method of pipe the >> output to a file and read that instead (Lines 60-79). I still need to try >> RUBY.EXE instead of RUBYW.EXE and see if it makes a difference. >> > > Looks like RUBY.EXE will fix my issue as per Puppet Bug #21043. I'll > update my daemon.rb and repost. > https://projects.puppetlabs.com/issues/21043 > Yes, sadly rubyw.exe is broken in 1.9: http://bugs.ruby-lang.org/issues/7239 . Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA%2Bu97u%3DGpiMRZbe2YAhM6oEKiHa-YR6%3D9XM3-EPzL59Wp5Z6fw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
