Puppet users - Oct 2010 - Cron on SUSE Enterprise Linux

Hi,

we''re running 0.25.5 on SLES11 SP1 machines and are now noticing lots
of
clutter in root''s crontab. The packages are rolled from the
suse-specfile as distributed in the puppet tarball.

SUSE sees fit to drop a warning comment into /var/spool/cron/tabs/<user>
that state this:

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Thu Oct 28 13:36:12 2010)
# (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
Exp $)

When using crontab -e, this is hidden from the user (i.e. not in the
editable crontab).

Whenever puppet makes a change, it submits this comment as new content
somehow though, and it all piles up in the crontab.

Has anyone seen this and can give a hint how to keep this from
happening? From looking at OpenSUSE source packages, it doesn''t seem
like there is a specific patch to make cron work differently in SUSE
environments.

Thanks,
Felix

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Oct 28, 2010 at 4:52 AM, Felix Frank
<felix.frank@alumni.tu-berlin.de> wrote:
> Hi,
>
> we''re running 0.25.5 on SLES11 SP1 machines and are now noticing
lots of
> clutter in root''s crontab. The packages are rolled from the
> suse-specfile as distributed in the puppet tarball.
>
> SUSE sees fit to drop a warning comment into
/var/spool/cron/tabs/<user>
> that state this:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- installed on Thu Oct 28 13:36:12 2010)
> # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie
> Exp $)
>
> When using crontab -e, this is hidden from the user (i.e. not in the
> editable crontab).
>
> Whenever puppet makes a change, it submits this comment as new content
> somehow though, and it all piles up in the crontab.
>
> Has anyone seen this and can give a hint how to keep this from
> happening? From looking at OpenSUSE source packages, it doesn''t
seem
> like there is a specific patch to make cron work differently in SUSE
> environments.
Is this the same as this issue Felix?

https://projects.puppetlabs.com/issues/593

I''m particularly interested in whether Alan Barrett''s summary
at #12
accurately describes your issue.

We have a cluster of issues around the cron provider as you can see
from this saved search:

https://projects.puppetlabs.com/projects/puppet/issues?query_id=98

I''d say we''re going to try and address all of them in a
release, we
just haven''t worked out exactly what that is.



>
> Thanks,
> Felix
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Nigel Kersten
Product Manager, Puppet Labs
http://www.puppetlabs.com
Twitter: @nigelkersten

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.