Issue #3553 has been updated by Nick Fagerlund. Project changed from Puppet Documentation to Puppet Status changed from Accepted to Needs Decision
This is a behavior bug, not a documentation bug. Not only is the current behavior obviously broken (we should give a useful error message, not `"-":6: bad minute`, which doesn't even tell us what resource is involved), but the documented behavior (running every minute) is questionable at best and deranged at worst. I'll patch the type description for the final 2.6 release to say that periodic fields are required. ---------------------------------------- Bug #3553: Cron resource with no time fields throws useless error message https://projects.puppetlabs.com/issues/3553 Author: Darvin Denmian Status: Needs Decision Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Adding the following entry to a file : cron { "app": command => "nice -n -10 /usr/bin/php/var/www/public_html/rotinas/rotinas.php 2>&1>> /var/log/app.log", environment => "PATH=$PATH", user => root, } I got the following as you can see in attached file. (NF: snip!) debug: Flushing cron provider target root "-":6: bad minute errors in crontab file, can't install. -- 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.
