Hello,
This may have been asked before (apologies), however, did not find a
good way to implement a schedule for puppet runs for a speciifc day
(say weekend maintennace window).
Could anyone suggest a clever workaround for that ?
Thanks
Kanishka
--
You received this message because you are su
ive to trigger your runs.
>
> On Sep 29, 9:47 pm, Kanishka Hettiarachchi wrote:> Hello,
>
> > This may have been asked before (apologies), however, did not find a
> > good way to implement a schedule for puppet runs for a speciifc day
> > (say weekend maintennace window).
Thanks Matt. I That seems to be the approach.
On Oct 1, 1:04 pm, Matt wrote:
> You could write a custom fact to figure out the maintenance window. If
> its always at a specific time and day of the week then that should not
> be that hard to do.
>
> On Oct 1, 9:51 am, Kanishk
Anyone know how to test if a resource is scheduled in the current
run ? We are looking to leverage puppet to remediate during the
schedule and run reporting only ($noop=true) other times.
Any suggestions are appreciated.
Thanks
Kanishka
--
You received this message because you are subscribed to
Has anyone been able to setup a schedule for say 7 pm to 4 am next
day ? By default the range can not extgend beyond the day, but
wondering anyone had a workaround similar to 01:00 - 04:00, 19:00 -
23:39 ?
Thanks
Kanishka
--
You received this message because you are subscribed to the Google Gro
Hello all,
Have noticed puppet agent continue to write agent runtime output to /
var/log/messages, although $vardir, logdir default to /var/lib/puppet/
log, agent run logs keep getting writtent to system messages file. I
recall this question has been asked before but did not see a
resolution.
Is
Thanks so much for the input
On Nov 2, 2:57 pm, Christopher Wood
wrote:
> On Wed, Nov 02, 2011 at 11:45:11AM -0700, Kanishka Hettiarachchi wrote:
> > Hello all,
>
> > Have noticed puppet agent continue to write agent runtime output to /
> > var/log/messages, although $v
thanks a lot
On Nov 3, 3:44 am, Jo Rhett wrote:
> --logdest=/some/file/name on the cli, or set as a parameter in puppet.conf.
> Right now it appears your logdest is syslog.
>
> On Nov 2, 2011, at 11:45 AM, Kanishka Hettiarachchi wrote:
>
>
>
>
>
> > Have notic