Issue #2428 has been updated by Luke Kanies. Subject changed from cron target overwrites user value to cron should support non-user targets Status changed from Unreviewed to Accepted
This is essentially intended behaviour -- we currently only support user crontabs, rather than files, but this is a good idea to add and shouldn't be that much work. ---------------------------------------- Bug #2428: cron should support non-user targets http://projects.reductivelabs.com/issues/2428 Author: Alex Urbanowicz Status: Accepted Priority: Normal Assigned to: Category: cron Target version: Complexity: Unknown Affected version: 0.24.8 Keywords: In crontab resource target value overwrites user. I define following cron entry to be stored in /etc/cron.d/yum-wrapper.cron cron {"yum_check_update": command => "/usr/bin/yum check-update -R 25 > /dev/null", ensure => present, hour => 5, minute => 53, target => "/etc/cron.d/yum-wrapper.cron", user => root, } puppet wants to create it in general crontab of user /etc/cron.d/yum-wrapper.cron: notice: //Node[default]/yum/Cron[yum_cache_update]/ensure: created crontab: user `/etc/cron.d/yum-wrapper.cron' unknown Puppet version 0.24.8, running on CentOS 5.3. -- 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 -~----------~----~----~----~------~----~------~--~---
