On Thu, 01 Apr 2010 22:19:39 -0400, Isaac Christoffersen
wrote:
> We're using RHN Satellite server to manage our packages and we have a
> custom package channel for third-party packages. Unfortunately, some of
> the packages in the channel are unsigned.
>
> Is there a way to get the Package P
We're using RHN Satellite server to manage our packages and we have a
custom package channel for third-party packages. Unfortunately, some of
the packages in the channel are unsigned.
Is there a way to get the Package Provider for yum to use the nogpgcheck
option? Right now, I'm using an exe
On Thu, Apr 1, 2010 at 7:07 PM, Daniel Pittman wrote:
> Charles Johnson writes:
>
>> Daniel, I resolved the issue. One of my classes had duplicate 'ensure => '
>> lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a
>> RESOLVED about my discovery.
>
> Wow. Thanks so much for fin
Charles Johnson writes:
> Daniel, I resolved the issue. One of my classes had duplicate 'ensure => '
> lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a
> RESOLVED about my discovery.
Wow. Thanks so much for finding that! That sort of silent failure can drive
someone mad, a
What revision of puppet are you running? This doesn't work for me in
0.25.4 either. However ...
I'm going to take a wild guess and imagine you want to have 3
fileserver.conf files because of the need for differing 'path' items
per environment using the [files] block. Let me suggest an alternative
Maybe I sent this without fully testing, looks like plugins are now per
module? I created the directory plugiins under one of my modules and I dont
see the error anymore. Behaviour doesnt seem 100% correct (I am on .25.4)
-Chris
On Thu, Apr 1, 2010 at 4:44 PM, Christopher Johnston wrote:
> See
Seeing an error that I didn't get in .24 since my recent upgrade today. I
have pluginsync set to true, my fileserver conf is pointing to
/etc/puppet/plugins and my config file is using the default pluginsource of
puppet://puppet/plugins yet the client fails saying it can't find it. Did
the behavi
Which is the preferred serialization format with puppet .25? I have read
that marshal can be the fastest, curious.
-Chris
--
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 un
James Turnbull wrote:
> Welcome back to the Puppet release cycle - brought to you by the
> newly minted Puppet Labs.
>
> The 0.25.5 release is a maintenance release in the
> 0.25.x branch. It contains a number of bug fixes but also some
> performance enhancements including speed-ups to Puppet's gra
>
> define adduser ($shell, $group, $fullname, $ingroups="", $uid="", $home="")
> {
> group { $group :
> ensure => present
> }
>
> user { $name :
> ensure => present,
> comment => "$fullname",
> gid => "$group",
> groups => $ingroups,
> m
Hello John,
On Thu, Apr 1, 2010 at 5:16 AM, John Lyman wrote:
>> file { "/foo/*": mode => 700; }
>>
>> What comes close is:
>> file { "/foo": mode => 700, recurse => "true", recurselimit => 1; }
>
> I'm not sure if this will work (I've never tried to ignore the top
> level directory), but you ca
Hello ,
I solved this issue with the following modification:
define adduser ($shell, $group, $fullname, $ingroups="", $uid="", $home="") {
group { $group :
ensure => present
}
user { $name :
ensure => present,
comment => "$fullname",
gid =>
Hi All,
I'm trying to use different environment for my servers management. I'am
able to use different classes, modules... for each environment but I
can't find how to specify fileserver configuration for each environement.
Here is a piece of my configuration :
puppet.conf
[main]
logd
Daniel, I resolved the issue. One of my classes had duplicate 'ensure => '
lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a
RESOLVED about my discovery.
I appreciate your help.
Cheers--
Charles
On Thu, Apr 1, 2010 at 2:38 AM, Daniel Pittman wrote:
> Charles Johnson write
> file { "/foo/*": mode => 700; }
>
> What comes close is:
> file { "/foo": mode => 700, recurse => "true", recurselimit => 1; }
I'm not sure if this will work (I've never tried to ignore the top
level directory), but you can try:
file { "/foo": mode => 700, recurse => "true", recurselimit => 1,
2010/4/1 Smain Kahlouch
> Message initial
> De: Michael DeHaan
> Reply-to: puppet-users@googlegroups.com
> À: puppet-users@googlegroups.com
> Cc: James Turnbull
> Sujet: Re: [Puppet Users] Mongrel : Can't download files
> Date: Wed, 31 Mar 2010 10:17:24 -0400
>
>
>
> On Wed, M
Charles Johnson writes:
> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman wrote:
>
>> [...]
>>
>> Your client logs *still* show that there is no MOTD stuff being touched at
>> all; try this on the client that should manage MOTD and see what is output:
>>
>> puppetd --test --debug 2>&1 | grep
17 matches
Mail list logo
