Issue #3313 has been updated by Matt Chesler.

I'm experiencing this same issue with CentOS 5, Puppet version 2.6.0.
----------------------------------------
Bug #3313: puppet.conf option client=true/false doesn't seem to work
http://projects.puppetlabs.com/issues/3313

Author: christian c
Status: Accepted
Priority: Normal
Assignee: Jesse Wolfe
Category: plumbing
Target version: 
Affected version: 0.25.4
Keywords: 
Branch: 


Hi,
I'm using puppet 0.25.4 on OpenSuse 11.1.

Trying to run puppet as listening client only with "listen=true" and 
"client=false" options in puppet.conf doesn't seem to work. After restarting 
puppet with the new configuration, first thing it does is polling the 
puppetmaster and afterwards every 30min.

But if I start puppetd with --no-client parameter it polls the puppetmaster 
only after being triggered by a puppetrun-command coming from the master.

Additionally, if the option works again, you should add it to the configuration 
reference because right now it isn't mentioned.

My config: 
[puppetd]
        classfile = $vardir/classes.txt
        server = puppet
        localconfig = $vardir/localconfigi
        httplog  = $logdir/http.log
        listen = true
        noop = false
        client = false
        puppetdlog = $logdir/puppetd.log
        puppetport = 8139
        pluginsync = true



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to