0.25.4 fixed my issue, so that's cool. It'll be great to have the
--no-client option working in the puppet.conf file though, as i'm going to
have to hack the init.d script to get this option in :-s
On 4 March 2010 14:48, Michael DeHaan wrote:
> Somewhat OT -- I'm still due (overdue) to take pup
Somewhat OT -- I'm still due (overdue) to take puppetrun out back and
shoot^W and upgrade it to better support wildcarded hosts and non-LDAP
databases if not supplying the name, etc.
Look for some upgrades next week.
On Thu, Mar 4, 2010 at 7:31 AM, Matt wrote:
> On 4 March 2010 11:47, Daniel K
On 4 March 2010 11:47, Daniel Kerwin wrote:
> I've been using puppetrun for a while now and it works very good. Can
> you post the log messages on puppetmaster and client?
>
> I started to use it in 0.25.1 and never had problems.
>
> On Thu, Mar 4, 2010 at 11:53 AM, Matt wrote:
> > More puppet r
I've been using puppetrun for a while now and it works very good. Can
you post the log messages on puppetmaster and client?
I started to use it in 0.25.1 and never had problems.
On Thu, Mar 4, 2010 at 11:53 AM, Matt wrote:
> More puppet run woes, is anyone using this feature successfully?
> I've
More puppet run woes, is anyone using this feature successfully?
I've got it working so the master can trigger the runs, but the client
doesn't see any changes to do when the run is triggered.
On the client
# puppetd --test --noop
Shows the changes that are going to happen
On the master
# puppet