On Sun, Jun 24, 2012 at 03:45:50PM -0500, Kyle Sexton wrote:
> All,
>
> I'm curious what monitoring solutions everyone is using and recommend, some
> of the ones I've been looking at recently:
>
> Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive
> solution (have to have add
Hi Jeff,
> This is definitely a bug. The regular expression we're using to
> extract the common name (CN) from the distinguished name (DN) is
> /^.*?CN\s*=\s*(.*)/ [1]
>
> This is a greedy regular expression which explains why it's also
> grabbing the email address. I think we need to fix this
Hi Jeff,
>You may be running into a bug in Puppet but I'm not entirely sure yet...
>What web server are you using to terminate the SSL connection from the
>agent to the master? Is it simply the built in one provided by `puppet
>master` or are you using Apache or something?
SSL is
Hi Jeff
On Thu, May 31, 2012 at 08:55:29AM -0700, Jeff McCune wrote:
>There are two identities in Puppet that relate to the security model. The
>first identity is the certname and the second is the node name.
>Puppet uses the certname to construct the certificate.
>Everything else
Hello,
I'm currently integrating puppet with an external openssl based PKI and
I stumbled across a problem which looks like it may be a bug in puppet.
All my certificates contain an emailAddress field in the subject. Here
it is in the default format:
% openssl x509 -in mir.example.net.pem -noo
Hi Seph,
> Does anyone else have problems with the wiki? I feel kinda ungrateful
> complaining, but I generally find it very slow and thus very hard to
> use. And right now, it appears unresponsive.
>
Yup, I often find it very slow also.
Cheers,
A.
--
. __/_/_ w: http://darq.com/
. _
Peter Burkholder wrote:
> Is it this issue?
>
> http://projects.reductivelabs.com/issues/1511
>
> You need to have ruby-shadow library and restart puppetd.
Thanks for your reply Peter. Unfortunately this issue is talking about
the useradd provider and I was asking about pw (which is the only op
Hi all,
Can someone tell me what is the reason for the pw user provider not
supporting the password parameter? As far as I know one can pipe an
encrypted password string to pw and it will set it as expected.
As a workaround I'm using an exec to achieve this functionality:
define users::freeb
Parimi V. wrote:
> # /usr/local/ruby/bin/facter
> /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/
> operatingsystemrelease.rb:79: private method `chomp' called for
> nil:NilClass (NoMethodError)
> from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/
> util/resolution.rb:1
