Background: the vixie-cron documentation states (and crontab -e agrees) that leading whitespace in crontab files is acceptable, and it is simply ignored. It is therefore possible to have valid crontabs with indentation.
However, the puppet provider - crontab.rb - only allows for leading whitespace in actual *cron job* entries, and fails to properly parse *comments* or *environment variable* lines that have such leading whitespace. I've submitted a bug with additional details, however that bug was erroneously closed as a duplicate of a "parsefile destroys your files" bug, so I'm posting here in hopes that this may be re-opened: https://projects.puppetlabs.com/issues/9440 Note that this bug will certainly *lead to* the destruction of your (perfectly valid) crontab file, but that's just an unhappy side effect; the real problem is the cron provider failing to recognize valid syntax in crontabs to begin with. Jeremy -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
