[r...@xxxx ~]# rpm -V puppet
S.5....T  c /etc/puppet/puppet.conf
[r...@xxxx ~]# grep verbose /etc/init.d/puppet
[r...@xxxx ~]# grep verbose /etc/sysconfig/puppet
[r...@xxxx ~]# cat /etc/sysconfig/puppet
# The puppetmaster server
#PUPPET_SERVER=puppet

# If you wish to specify the port to connect to do so here
#PUPPET_PORT=8140

# Where to log to. Specify syslog to send log messages to the system log.
#PUPPET_LOG=/var/log/puppet/puppet.log

# You may specify other parameters to the puppet client here
#PUPPET_EXTRA_OPTS=--waitforcert=500

I'm not really seeing anything giving it the verbose option...
nothing's been modified from EPEL other than the
/etc/puppet/puppetd.conf line:

    report = true


Thanks.


On Tue, Mar 9, 2010 at 4:57 PM, Todd Zullinger <t...@pobox.com> wrote:
> Kent Rankin wrote:
>> Installed the EPEL package... it runs it as a daemon without options.
>> Here's the output from ps -ef|grep puppet:
>>
>> root     10249     1  0 Mar08 ?        00:02:17 /usr/bin/ruby
>> /usr/sbin/puppetd --verbose
>
> That --verbose is what's causing this I think.  That's not part of the
> default EPEL setup AFAIK.  What is the output of rpm -V puppet ?  If
> /etc/sysconfig/puppet is modified, check if verbose is added to the
> puppet options there.
>
> Also check in /etc/puppet/puppet.conf for verbose = true (though that
> wouldn't manifest itself in the command line options).
>
> --
> Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> The chains of habit are too weak to be felt until they are too strong
> to be broken
>    -- Samuel Johnson (1709-1784)
>
>

-- 
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.

Reply via email to