On Feb 2, 3:34 pm, jcbollinger <john.bollin...@stjude.org> wrote:
>
> You are missing something, I think. The 'schedule' metaparameter can
> be used with any resource, including those of defined types.
>
> Could it be as simple as the fact that you name your schedule
> 'morning', but assign a different, possibly missing, schedule 'einmal'
> to the resource?
>
> Anyway, you didn't specify what "does not work" means. What is the
> nature of the [mis]behavior you see? Is it possible that you have the
> wrong expectations? Schedules in Puppet limit when or how often
> resources are managed, but that's modulated by when and how often the
> node checks in to request a catalog.
>
> John
Ah, I am sorry. You are absolutly right! I have a typo in my example.
Actually I use the schedule "morning" in my resource.
Perhaps some background is useful: the define "my_crontab" is using a
"cron" type in the background.
When I did some tests, I inserted the schedule in the "cron" part and
it worked. But when I try to use the schedule directly in the call of
the define "my_crontab" (like in the example), it does not work.
I am expecting in the example above that the resource my_crontab{"user-
crontab"} is only activated during 8 and 9'o clock, assuming there is
a puppet run at this time.
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
