Since I stumpled upon this bug I added the --no-client flag to the
puppet init script. Apart from being a bit ugly, it works fine.
It looks like this:
checkproc $puppetd --no-client --logdest /var/log/puppet/puppetd.log $
{PUPPET_OPTS} ${PUPPET_EXTRA_OPTS} && touch ${lockfile}I also added logdest in this example as it doesn't seem to work from the config file either but there should be a report around I guess. Christian On 9 Sep., 05:19, Chad Huneycutt <chad.huneyc...@gmail.com> wrote: > The --no-client flag to puppetd didn't work for you? My understanding > of the bug is just that the client=false option isn't respected, but > if you specify it on the command line, it works fine. Right? > > - Chad > > > > On Tue, Sep 7, 2010 at 4:54 PM, CraftyTech <hmmed...@gmail.com> wrote: > > Has anyone found a workaround for this? It appears that the bug > > hasn't been fixed. I basically just need the daemon to run, > > listening, without ever calling the puppetmaster on its own. My > > clients are configured as follow: > > > *************************** > > [puppetd] > > report = true > > listen = true > > client = false > > > *************************** > > Cheers, > > > Henry > > > On Aug 3, 1:35 pm, CraftyTech <hmmed...@gmail.com> wrote: > >> Gotcha.. thanks, > > >> On Aug 3, 1:27 pm, Chad Huneycutt <chad.huneyc...@gmail.com> wrote: > > >> > There is a bug (http://projects.puppetlabs.com/issues/3313) about this. > > >> > On Tue, Aug 3, 2010 at 1:06 PM,CraftyTech<hmmed...@gmail.com> wrote: > >> > > Hello, > > >> > > I have my clients' puppet.conf file setup as: > > >> > > [puppetd] > >> > > report = true > >> > > listen = true > >> > > client = false > > >> > > But the client keeps on checking in every 30 mins. I understand from > >> > > other posts that puppetd works fine with the --no-client flag, but is > >> > > there a work around for this? or is it address in the next release > >> > > (0.26)? > > >> > > My current setup: > >> > > CentOS: 5.4 > >> > > Puppet: 0.25.5 > > >> > > Thanks, > > >> > > -- > >> > > You received this message because you are subscribed to the Google > >> > > Groups "Puppet Users" group. > >> > > To post to this group, send email to puppet-us...@googlegroups.com. > >> > > To unsubscribe from this group, send email to > >> > > puppet-users+unsubscr...@googlegroups.com. > >> > > For more options, visit this group > >> > > athttp://groups.google.com/group/puppet-users?hl=en. > > >> > -- > >> > Chad M. Huneycutt > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/puppet-users?hl=en. > > -- > Chad M. Huneycutt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
