#593: Puppet's cron type struggles with vixie-cron
----------------------+-----------------------------------------------------
Reporter: rainhead | Owner: luke
Type: defect | Status: assigned
Priority: normal | Milestone: elmo
Component: cron | Version: 0.22.3
Severity: normal | Resolution:
Keywords: cron | Stage: Accepted
Patch: None | Complexity: Unknown
----------------------+-----------------------------------------------------
Changes (by luke):
* component: types => cron
Old description:
> After making a few changes to my cron job in my manifest, my crontab
> begins to look like:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- installed on Thu Apr 12 12:16:01 2007)
> # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
> Exp $)
> # HEADER This file was autogenerated at Thu Apr 12 12:16:01 -0700 2007 by
> puppet.
> # HEADER While it can still be managed manually, it is definitely
> notrecommended.
> # HEADER Note particularly that the comments starting with 'Puppet Name'
> should
> # HEADER not be deleted, as doing so could cause duplicate cron jobs.
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- installed on Wed Apr 11 16:42:40 2007)
> # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
> Exp $)
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- installed on Tue Apr 10 13:49:45 2007)
> # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
> Exp $)
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- installed on Thu Apr 5 17:36:42 2007)
> # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
> Exp $)
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.XXXXWxMPKB installed on Thu Apr 5 17:08:07 2007)
> # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
> Exp $)
> # Puppet Name: websync
> */10 * * * * <snip>
>
> If puppet would put its notice just before the first job it manages, I
> think it would avoid this problem.
New description:
After making a few changes to my cron job in my manifest, my crontab
begins to look like:
{{{
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Thu Apr 12 12:16:01 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
Exp $)
# HEADER This file was autogenerated at Thu Apr 12 12:16:01 -0700 2007 by
puppet.
# HEADER While it can still be managed manually, it is definitely
notrecommended.
# HEADER Note particularly that the comments starting with 'Puppet Name'
should
# HEADER not be deleted, as doing so could cause duplicate cron jobs.
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Wed Apr 11 16:42:40 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Tue Apr 10 13:49:45 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Thu Apr 5 17:36:42 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.XXXXWxMPKB installed on Thu Apr 5 17:08:07 2007)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
Exp $)
# Puppet Name: websync
*/10 * * * * <snip>
}}}
If puppet would put its notice just before the first job it manages, I
think it would avoid this problem.
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/593#comment:3>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
