Hi Peter,
Peter Meier schrieb:
>> i am using puppet 0.25.4 at debian lenny and i have got a question about
>> the cron type. If i use something like that, the cron will be stored at
>> "/etc/cron.daily/get-selections".
>
>> cron { "get-slections":
>> command => "/usr/bin/d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> i am using puppet 0.25.4 at debian lenny and i have got a question about
> the cron type. If i use something like that, the cron will be stored at
> "/etc/cron.daily/get-selections".
>
> cron { "get-slections":
> command
Hello,
i am using puppet 0.25.4 at debian lenny and i have got a question about
the cron type. If i use something like that, the cron will be stored at
"/etc/cron.daily/get-selections".
cron { "get-slections":
command => "/usr/bin/dpkg --get-selections >
/var/backups/get-s
Just ran into a dependency issue with 0.24.8. The system was trying
to add a crontab entry for a user it had not yet created. I do have
the user being created with the user type.
I started to look into the code and it seems the user is not setup
with autorequire. My question is should it
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
