Thanks for both solutions. :) Looks like either will work for me.
--
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+un
bobics wrote:
> I'd like to pass command line options for a package installed via a
> gem provider. In particular, I'm updating puppet, the equivalent
> command would be:
>
> /usr/bin/gem1.8 install puppet -v=2.6.1 --no-rdoc --no-ri
>
> (The extra docs that gets installed with puppet take WA
Also for the record.
We've experienced the banning - but only for RHEL4 hosts (which use
up2date) and not RHEL5 (which use yum).
Our solution while we still have RHEL4 hosts and haven't implemented RedHat
Satellite or Spacewalk was to push the runinterval out to 14400 for these
hosts. This matche
On Thu, Nov 4, 2010 at 4:55 PM, bobics wrote:
> I'd like to pass command line options for a package installed via a
> gem provider. In particular, I'm updating puppet, the equivalent
> command would be:
>
> /usr/bin/gem1.8 install puppet -v=2.6.1 --no-rdoc --no-ri
>
> (The extra docs that gets
I'd like to pass command line options for a package installed via a
gem provider. In particular, I'm updating puppet, the equivalent
command would be:
/usr/bin/gem1.8 install puppet -v=2.6.1 --no-rdoc --no-ri
(The extra docs that gets installed with puppet take WAY too long and
are unnecessa
http://docs.puppetlabs.com/guides/introduction.html
On Thu, Nov 4, 2010 at 2:27 PM, Russell Perkins <
rperk...@digitalshiftstudios.com> wrote:
> I installed factor and puppet but it didn't seem to make an /etc/
> puppet/ is this something I have to manually create or did I mess up
> my install so
I installed factor and puppet but it didn't seem to make an /etc/
puppet/ is this something I have to manually create or did I mess up
my install somehow?
It was pretty simple to install but maybe I missed something, "ruby
install.rb" for both factor and puppet
--
You received this message beca
I'm trying to install 2 packages where 2nd packages replaces certain
files from first packages.
package { "jboss":
provider => yum,
ensure => latest
}
package { "jboss-fix":
provider => yum,
ensure => latest
}
This seems to error ou
On Nov 4, 2010, at 11:10 AM, jogui wrote:
> Hi!
>
> use case :
>file { "x" : source => "puppet:///path/to/file" }
> works fine, source is translated.
>
> but use case :
>file { "x" : source => extlookup('myvar') }
>
> set source to "puppet:///path/to/file" without translation when csv
Hi!
use case :
file { "x" : source => "puppet:///path/to/file" }
works fine, source is translated.
but use case :
file { "x" : source => extlookup('myvar') }
set source to "puppet:///path/to/file" without translation when csv
file contains
myvar,puppet:///path/to/file
How to use pu
On 11/04/2010 01:16 PM, PBWebGuy wrote:
We just ran into a condition when a templatized configuration file
would get replaced with something that I had no clue where it came
from and the content is no where in the puppet source tree. On
subsequent updates the proper file would appear. I've bee
We just ran into a condition when a templatized configuration file
would get replaced with something that I had no clue where it came
from and the content is no where in the puppet source tree. On
subsequent updates the proper file would appear. I've been able to
consistently reproduce the probl
It sure sounds like you need to be distributing a canonical
/etc/passwd, /etc/shadow, and /etc/groups on every puppet run.
* hywl51 [2010/11/04 03:11]:
> Yes, you said it. Unfortunately, we have some users running as
> root privilege on server, because they cann't work without it.
>
> But we do
On 11/04/2010 10:40 AM, Martin Alfke wrote:
>
> On Nov 4, 2010, at 8:28 AM, hywl51 wrote:
>
>> Hi, all
>>
>> I want to control the user accounts on our company servers with
>> puppet. The complete requirements are the following:
>>
>> 1. Assuming that one user run " useradd " on the server to
On Nov 4, 4:34 am, Patrick wrote:
> On Nov 4, 2010, at 12:28 AM, hywl51 wrote:
>
> > Hi, all
>
> > I want to control the user accounts on our company servers with
> > puppet. The complete requirements are the following:
>
> > 1. Assuming that one user run " useradd " on the server to create
On Nov 4, 12:03 pm, Felix Frank
wrote:
>
>
> This is not a network or name resolution issue; your manifest contains
> no node definition that fits your client machine.
>
> Regards,
> Felix
Felix, holy cow! All that effort and it was a typo. I use a regex to
group my nodes and I typo'ed on the dom
On 11/04/2010 12:46 PM, theirpuppet wrote:
> I have a series of hosts that sit on multiple networks. The
> puppetmaster does so as well. The private internal network is for AD
> and backups, the external is for public services. I was able to setup
> a test host that only accesses the external netwo
I have a series of hosts that sit on multiple networks. The
puppetmaster does so as well. The private internal network is for AD
and backups, the external is for public services. I was able to setup
a test host that only accesses the external network. All's great
there. But when I added a real host
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
They were produced from the expanded-relationships.dot.
Glad to hear that there's a fix on the way, we're really liking the
potential of stages!
Trevor
On 11/03/2010 07:55 PM, Luke Kanies wrote:
> On Nov 3, 2010, at 10:02 AM, Trevor Vaughan wrote:
>
Hi, all
I follow the offical install instructions and place auth.pp into /etc/
puppet/modules/ssh/manifests/.
offical site:
http://projects.puppetlabs.com/projects/puppet/wiki/Module_Ssh_Auth_Patterns
But I got the following error when running puppet:
err: Could not retrieve catalog from remot
Yes, you said it. Unfortunately, we have some users running as root
privilege on server, because they cann't work without it.
But we don't want them to add new users on their own, so we hope find
a way that will delete all illegal users on the system every 30
minute.
On Nov 4, 5:02 pm, Matt Wa
On Thursday 04 Nov 2010 10:40:02 Martin Alfke wrote:
> On Nov 4, 2010, at 8:28 AM, hywl51 wrote:
> > Hi, all
> >
> > I want to control the user accounts on our company servers with
> > puppet. The complete requirements are the following:
> >
> > 1. Assuming that one user run " useradd " on th
If puppet can not fullfill this requirement, is there any other tool
or solution to solve it?
On Nov 4, 5:34 pm, Patrick wrote:
> On Nov 4, 2010, at 12:28 AM, hywl51 wrote:
>
> > Hi, all
>
> > I want to control the user accounts on our company servers with
> > puppet. The complete requirements ar
On Nov 4, 2010, at 8:28 AM, hywl51 wrote:
> Hi, all
>
> I want to control the user accounts on our company servers with
> puppet. The complete requirements are the following:
>
> 1. Assuming that one user run " useradd " on the server to create
> a new account named "newuser".
> 2. Puppet w
On Nov 4, 2010, at 12:28 AM, hywl51 wrote:
> Hi, all
>
> I want to control the user accounts on our company servers with
> puppet. The complete requirements are the following:
>
> 1. Assuming that one user run " useradd " on the server to create
> a new account named "newuser".
> 2. Puppet
Hi, all
I want to control the user accounts on our company servers with
puppet. The complete requirements are the following:
1. Assuming that one user run " useradd " on the server to create
a new account named "newuser".
2. Puppet will konw the new user created soon, and restore the server
s
26 matches
Mail list logo
