Issue #2127 has been updated by gwar9999.
Then I'm not sure why when puppet compares the entry in the crontab (that it previously inserted) and the current template result why it considers them to be different. If puppet produced the prior crontab and the new crontab why wouldn't they be identical? That is, either they both should have a newline or they both shouldn't. The current implementation is that one does and one doesn't which appears to be a bug. ---------------------------------------- Bug #2127: cron resource adds newline when compiled from a template http://projects.reductivelabs.com/issues/2127 Author: gwar9999 Status: Rejected Priority: Normal Assigned to: Category: cron Target version: Complexity: Trivial Affected version: 0.24.7 Keywords: If the template consists of a single line that does not end with a templated variable or ruby code snippet then a newline is added to the cron command. This causes an issue when puppet reapplies it's configuration since it always compares "cmd" with "cmd\n" and thus recreates the crontab each time it runs. if template contains "/bin/true" then a newline is appended. However, if the template ends with a -%> then the newline is suppressed, so the following workaround suffices "/bin/true <% "" -%>. This hack isn't elegant nor obvious, but it appears to work. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
