Hi, is there a way to manage cron jobs by puppet with the builtin cron ressource in extra files? I use to manage my cron jobs below /etc/cron.d and a service own name, for example /etc/cron.d/apache (which can contain many jobs). If I remove my service apache from the system or migrate it to another machine I have exactly one cron dependency so it is very easy to manage. I know, puppet manages my jobs but I like it that the system has the same structure as without puppet (for example if I had to remove puppet for some reason). I don''t see a way to do that in puppet but maybe I don''t understand the documentation. regards Oli
Hi, is there a way to manage cron jobs by puppet with the builtin cron ressource in extra files? I use to manage my cron jobs below /etc/cron.d and a service own name, for example /etc/cron.d/apache (which can contain many jobs). If I remove my service apache from the system or migrate it to another machine I have exactly one cron dependency so it is very easy to manage. I know, puppet manages my jobs but I like it that the system has the same structure as without puppet (for example if I had to remove puppet for some reason). I don''t see a way to do that in puppet but maybe I don''t understand the documentation. regards Oli
I use the same layout and the only way it works for me was to create file resources and distribute the files directly. After distribution i call check_system_crontabs to rebuild the crontab based on cron scripts in /etc/cron.d ... afaik there''s no way to use the cron type to accomplish this layout On Feb 2, 3:15 pm, Oliver Schad <pup...@oschad.de> wrote:> Hi, > > is there a way to manage cron jobs by puppet with the builtin cron > ressource in extra files? > > I use to manage my cron jobs below /etc/cron.d and a service own name, for > example /etc/cron.d/apache (which can contain many jobs). > > If I remove my service apache from the system or migrate it to another > machine I have exactly one cron dependency so it is very easy to manage. > > I know, puppet manages my jobs but I like it that the system has the same > structure as without puppet (for example if I had to remove puppet for > some reason). > > I don''t see a way to do that in puppet but maybe I don''t understand the > documentation. > > regards > Oli > > signature.asc > < 1KViewDownload-- 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.
Please ignore, sorry for the double posting
Am Tuesday 02 February 2010 schrieb mir Daniel Kerwin:> I use the same layout and the only way it works for me was to create > file resources and distribute the files directly. After distribution i > call check_system_crontabs to rebuild the crontab based on cron > scripts in /etc/cron.d ... > > afaik there''s no way to use the cron type to accomplish this layoutOk, so maybe we could make a feature request - I think it is a very common cron job design. regards Oli
Zitat von Oliver Schad <puppet@oschad.de>:> Am Tuesday 02 February 2010 schrieb mir Daniel Kerwin: >> I use the same layout and the only way it works for me was to create >> file resources and distribute the files directly. After distribution i >> call check_system_crontabs to rebuild the crontab based on cron >> scripts in /etc/cron.d ... >> >> afaik there''s no way to use the cron type to accomplish this layout > > Ok, so maybe we could make a feature request - I think it is a very common > cron job design.don''t hesitate to open one. cheers pete -- 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.