Hi All, I''m very happily using puppet in a large environment, but I ran into a problem: In our environment, we create multiple root accounts (via NIS), so that each UNIX admin can have a root-priveledge account, but with their own password. This is presenting a problem in using puppet to manage root-owned cron jobs. On RHEL linux, puppet is running ''crontab -l'', ''crontab -r'', etc without specifying the -u root argument. This causes crontab to go lookup the owner of UID zero, which can return any number of names. This causes multiple crontab files to be created, under different names, all of which execute, causing mass confusion. I see from the sources of the crontab filetype that -u will be specified if the user specified differs from the process UID. Is there any way to work around this, to get puppet to always specify the -u argument? Thanks, Erik Burrows --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
That is a tough one, try creating your own custom type as a monkey patch. What happens if you add a user => "root" to your manifest for the cron entry? -Jason --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I''m not trying to be snarky and I''m no sysadmin, but why do you do this instead of using sudo? On Tue, Nov 25, 2008 at 7:42 PM, jrojas <jason@nothingbeatsaduck.com> wrote:> > That is a tough one, try creating your own custom type as a monkey > patch. > > What happens if you add a user => "root" to your manifest for the cron > entry? > > -Jason > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
that and running root logins over NIS... 2008/11/25 Andrew Shafer <andrew@reductivelabs.com>> > I''m not trying to be snarky and I''m no sysadmin, but why do you do this > instead of using sudo? > > > > On Tue, Nov 25, 2008 at 7:42 PM, jrojas <jason@nothingbeatsaduck.com>wrote: > >> >> That is a tough one, try creating your own custom type as a monkey >> patch. >> >> What happens if you add a user => "root" to your manifest for the cron >> entry? >> >> -Jason >> >> > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---