Issue #4769 has been updated by Nigel Kersten.
I'm perfectly happy with 0 (and perhaps a munge in the type to coerce negative values to 0 with a deprecation warning) but I'm concerned about the ancient Ruby versions we support. I won't be surprised at all if it turns out that 0 fails on old RHEL ruby :( ---------------------------------------- Bug #4769: Ruby timeout module doesn't support negative values anymore http://projects.puppetlabs.com/issues/4769 Author: Nigel Kersten Status: Accepted Priority: Normal Assignee: Category: Target version: Affected version: 0.25.5 Keywords: Branch: Given this manifest. <pre> # cat /tmp/test.pp exec { "dpkg_configure_all": environment => "DEBIAN_FRONTEND=noninteractive", command => "/usr/bin/dpkg --configure -a --force-confold", timeout => "-1", } </pre> as according to the docs a negative timeout disables the timeout. <pre> r...@nigelk-vm1:~/maverick/ruby1.8-1.8.7.299# puppet -v --factpath /nofacts /tmp/test.pp info: Applying configuration version '1284498507' err: //Exec[dpkg_configure_all]/returns: change from notrun to 0 failed: time interval must be positive This wasn't the case for 0.25.4 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
