[Puppet Users] Re: template command

[Bjørn Dyresen]

On Jul 25, 2009, at 2:09 AM, lance dillon wrote:

>
>
>> Try with something like:
>>
>> <%- if role == "fast" -%>
>><%- line =  "The line you want to print" -%>
>> <%- end -%>
>> <%= line -%>
>>
>>
>
> A bit to quick there. For this to work you have to feed the template  
> with the variable. You can just feed $role with a default value. eg  
> default..
>
>
> The thing is I have a lot of node definitions, and every node  
> includes this class.  I don't want to have to edit every node  
> definition in order to get that line in just a couple of nodes.
>
> Maybe change the class so it concats another template/file onto the  
> end of it if $role is set, although I'm not quite sure how to do  
> that yet without experimentation.
>
>

You dont have to specify it on every node. Thats what a default value  
is for.

Take this as an example:

define your_definition($role=default) {
 file { "/path/to/your/file":
 ensure => present,
 content => template("your_template")
 }
}

Now, if you call it with

your_definition { "resource_name": }

$role will have the value "default" in your template

if you call it with

your_definition { "resource_name":
 role => "fast",
}

your $role will have the value fast




Not what you want, since you would have to flick a switch on your node  
definition, but I tend to deal these issues like this:



class yourmodulename {

 $role = "default"

 your_definition { "resource_name":
 role => "$role",
 }
}

define yourmodulename::your_definition($role=default) {
 file { "/path/to/file/to/controll":
 ensure => present,
 content => template("yourmodulename/templatename")
 }
}









Then you can subclass this and override the $role=default

So the subclass in the module would look like:


class yourmodulename::yoursubclass inherits yourmodulename {

 $role = "fast"

 Your_definition['resource_name']  { role => "$role" }
}



In that case every place you include the subclass the template is fed  
with "fast" as the value for $role. Im sure you can find other ways to  
deal with it all well.



Regards



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: template command

[lance dillon]

Try with something like:
>
> <%- if role == "fast" -%>
><%- line =  "The line you want to print" -%>
> <%- end -%>
> <%= line -%>
>
>
>
> A bit to quick there. For this to work you have to feed the template with
> the variable. You can just feed $role with a default value. eg default..
>
>
The thing is I have a lot of node definitions, and every node includes this
class.  I don't want to have to edit every node definition in order to get
that line in just a couple of nodes.

Maybe change the class so it concats another template/file onto the end of
it if $role is set, although I'm not quite sure how to do that yet without
experimentation.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Notifying a service when exported resources go away

[Teyo Tyree]

On Fri, Jul 24, 2009 at 12:47 PM, Eric Gerlach
wrote:

>
> Hi,
>
> I'm working with nagios, and if I'm de-configuring a server manually, I'd
> like
> to have the monitoring system not complain about it vanishing.
>
> So, for each host I have:
>
>@@nagios_host { "$fqdn":
>use => "generic-host",
>address => $fqdn,
>contact_groups => "itstaff",
>notify => Service["nagios3"]
>}
>
> and then on the Nagios server I have:
>
>resources { "nagios_host":
>purge => true,
>notify => Service["nagios3"]
>}
>
>Nagios_host <<| |>>
>
> If I don't have a notify on the resources entry, the nagios host entries go
> away, but nagios doesn't refresh.  If I have it on the resources entry, it
> makes the service depend on it, and so won't purge:
>
> "Service[nagios3] still depends on me -- not purging"
>
> Is it possible to accomplish what I'm trying to do?  If so, how?
>
> Cheers,
>
> --
> Eric Gerlach, Network Administrator
> Federation of Students
> University of Waterloo
> p: (519) 888-4567 x36329
> e: egerl...@feds.uwaterloo.ca
>
> >
>
Eric the most straight forward mechanism is to purge all the resources
associated with the host that is being decommissioned.  There is a script to
do this attached to the wiki page for storedconfigs.
http://reductivelabs.com/trac/puppet/attachment/wiki/UsingStoredConfiguration/kill_node_in_storedconfigs_db.rb

Cheers,
Teyo

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] command to list intra-class references?

[eagleheart]

Hi,

If I have a resource in a class like

file { somefile:
 ensure => present,
... }

Is there a puppet command to list any reference to it, e.g. -
" require => File[somefile] "
- among all the class definitions?

Of course there's always unix grep, but a puppet command would be
nicer.

TIA

John

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Best Practices Rewrite - First Draft

[Digant C Kasundra]

> * Environments and the workflow surrounding them
> 
> There is already UsingMultipleEnvironments, which has all the
> technical 
> stuff. Perhaps a few sentences about how to use the production,
> testing, 
> and development environment.

I'd love to be able to update that down the line (probably later this year when 
we move to 0.25 and start using the environment support).  We had some very 
specific ideas in mind for our use of environments with Git which i think may 
be particularly useful for those institutions such as ours where we have formal 
change management processes and vetting required from multiple stakeholders in 
different departments, making fullscale migration difficult.  I'll see if i can 
draft something up.

-- 
Digant C Kasundra 
Technical Lead, ITS Unix Systems and Applications, Stanford University

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Best Practices Rewrite - First Draft

[Digant C Kasundra]

- "Paul Lathrop"  wrote:

> Hi Puppeteers,
> 
> I spent some time tonight making a first pass at what I hope will
> eventually be a good replacement for the current "Puppet Best
> Practices" page on the wiki. I know this needs *tons of work, but I
> hit a good pausing point and decided it was time to ask for feedback
> and contributions. The idea here is to provide some overall
> guidelines
> to help newcomers to Puppet establish good habits as well as get the
> most out of Puppet, and especially to highlight some common mistakes
> and how to avoid them.
> 
> Please take a look and flame away. I need feedback, both positive and
> negative, as well as input as to what the Best Practices actually are
> (Volcane, I'm looking at you!). I especially need to flesh out that
> final section.

I was hoping to redraft this myself when 0.25 came out, but looks like you've 
beat me to it.  Sadly, time doesn't allow me to follow up as closely with the 
user list as I'd like, (my participation with Puppet as been limited lately to 
the asynchronous storeconfigs work we've contracted).

Here are some comments to consider:

* A lot of this does read more like an introduction to Puppet and Puppet 
concepts, so some of this might need to be broken away elsewhere.
* While classes aren't object-oriented, I think treating them as if they are 
isn't necessarily a bad thing either.  Ultimately, when you inherit you are 
only given yourself permission to override the declared resources, but I also 
find it to be a good idea to keep this kind of modeling to properly represent 
what is happening.  Ergo, when one class is a derivative of another, I find it 
better to inherit instead of include, even if I am not overriding a declared 
resource, simply because modeling shouldn't be a function of what features you 
are using.
* While one shouldn't overuse dependencies, I wouldn't put notify and subscribe 
in the same boat since they are functionally useful for things besides trying 
to make Puppet do something in a particular order.  I think the intent was just 
to relate the two parameters to before and require but I would recommend 
removing it or relocating it so we don't give the impression that using notify 
or subscribe is a bad idea.
* Because of complexity of how and when classes are interpreted, aren't 
variables often a tricky thing to play with if you are planning to change their 
values in later scopes?
* Lastly, perhaps this is still my OCD, but I'm still a fan of the style guide. 
 Without it, I dont' think our manifests would be as clean and legible as they 
currently are.


-- 
Digant C Kasundra 
Technical Lead, ITS Unix Systems and Applications, Stanford University

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: template command

[Bjørn Dyresen]

On Jul 24, 2009, at 11:27 PM, Bjørn Dyresen wrote:

>
> On Jul 24, 2009, at 10:17 PM, lance dillon wrote:
>
>> I need to be able to include a line in a template, based on  
>> presence and value of a variable, something like this:
>>
>> #  file.erb
>> blah
>> blah blah
>> <% if role == "fast" -%>
>> this line is here now
>> <% end -%>
>>
>>
>>
>> I only want the line to be included if $role exists and is equal to  
>> fast.  If $role doesn't exist, or doesn't equal "fast", it  
>> shouldn't include the line:
>>
>> Jul 24 19:59:40 lonengbld01 puppetmasterd[3095]: Failed to parse  
>> template repo/R
>> edHat-4/extras.repo: Could not find value for 'role' at /etc/puppet/ 
>> modules/repo
>> /manifests/init.pp:121 on node blah
>>
>> What would be the correct syntax?
>>
>> Thanks
>>
>>
>
> Try with something like:
>
> <%- if role == "fast" -%>
><%- line =  "The line you want to print" -%>
> <%- end -%>
> <%= line -%>
>
>

A bit to quick there. For this to work you have to feed the template  
with the variable. You can just feed $role with a default value. eg  
default.. 
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: template command

[Bjørn Dyresen]

On Jul 24, 2009, at 10:17 PM, lance dillon wrote:

> I need to be able to include a line in a template, based on presence  
> and value of a variable, something like this:
>
> #  file.erb
> blah
> blah blah
> <% if role == "fast" -%>
> this line is here now
> <% end -%>
>
>
>
> I only want the line to be included if $role exists and is equal to  
> fast.  If $role doesn't exist, or doesn't equal "fast", it shouldn't  
> include the line:
>
> Jul 24 19:59:40 lonengbld01 puppetmasterd[3095]: Failed to parse  
> template repo/R
> edHat-4/extras.repo: Could not find value for 'role' at /etc/puppet/ 
> modules/repo
> /manifests/init.pp:121 on node blah
>
> What would be the correct syntax?
>
> Thanks
>
>

Try with something like:

<%- if role == "fast" -%>
 <%- line =  "The line you want to print" -%>
<%- end -%>
<%= line -%>


Regards



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Source Arrays and Template Arrays

[jb]

It doesn't seem to work from me, bombing out if the template specified
first doesn't exist.  you'd expect it to gracefully ignore and try the
next...this a bug?  running puppet-0.24.6-1.1


On Jul 23, 12:31 pm, Udo Waechter 
wrote:
> hmmm, right after sending the provious mail, I realised something:
>
> On 23.07.2009, at 21:27, Udo Waechter wrote:
>
>
>
> > Hi,
>
> > On 23.07.2009, at 19:58, TomTom wrote:
>
> >> Is it possible to do the same thing with templates?
> >> An example of what I want to do is:
>
> >> file { "/etc/sysctl.conf":
> >> content => [
> >>  template("sysctl.conf.$hostname.erb"),
> >>  template("sysctl.conf.$tuningpolicy.erb"),
> >>  template("sysctl.conf.erb"),
> >> ]
> >> }
>
> > Unfortunately, the behaviour here is different. All templates  
> > outputs are concatenated...
>
> > see:http://reductivelabs.com/trac/puppet/wiki/FunctionReference#template
>
> this is different call:
>
> file{"/foo/bar":
>         content => template("template1","template2")
>
> }
>
> yields concatenated templates.
>
> maybe this:
> file { "/etc/sysctl.conf":
> content => [
>    template("sysctl.conf.$hostname.erb"),
>    template("sysctl.conf.$tuningpolicy.erb"),
>    template("sysctl.conf.erb"),
>   ]
>
> }
>
> works as expected, namely to select the one template that exists (or  
> the first that exists).
>
> dunno,
> udo.
>
> --
> :: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
> :: genuine input for your ears:http://auriculabovinari.de
> ::                          your eyes:http://ezag.zoide.net
> ::                          your brain:http://zoide.net
>
>  smime.p7s
> 2KViewDownload
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] template command

[lance dillon]

I need to be able to include a line in a template, based on presence and
value of a variable, something like this:

#  file.erb
blah
blah blah
<% if role == "fast" -%>
this line is here now
<% end -%>



I only want the line to be included if $role exists and is equal to fast.
If $role doesn't exist, or doesn't equal "fast", it shouldn't include the
line:

Jul 24 19:59:40 lonengbld01 puppetmasterd[3095]: Failed to parse template
repo/R
edHat-4/extras.repo: Could not find value for 'role' at
/etc/puppet/modules/repo
/manifests/init.pp:121 on node blah

What would be the correct syntax?

Thanks

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Notifying a service when exported resources go away

[Eric Gerlach]

Hi,

I'm working with nagios, and if I'm de-configuring a server manually, I'd like
to have the monitoring system not complain about it vanishing.

So, for each host I have:

@@nagios_host { "$fqdn":
use => "generic-host",
address => $fqdn,
contact_groups => "itstaff",
notify => Service["nagios3"]
}

and then on the Nagios server I have:

resources { "nagios_host":
purge => true,
notify => Service["nagios3"]
}

Nagios_host <<| |>>

If I don't have a notify on the resources entry, the nagios host entries go
away, but nagios doesn't refresh.  If I have it on the resources entry, it
makes the service depend on it, and so won't purge:

"Service[nagios3] still depends on me -- not purging"

Is it possible to accomplish what I'm trying to do?  If so, how?

Cheers,

-- 
Eric Gerlach, Network Administrator
Federation of Students
University of Waterloo
p: (519) 888-4567 x36329
e: egerl...@feds.uwaterloo.ca

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd no-daemonize

[Derek Yarnell]

--test does do the right thing and doesn't
fork a copy into the background and does what I need it to do running
the built in version of ruby  (1.8.1) or running the new ruby (1.8.7).
Anyway thanks again,
derek

On Fri, Jul 24, 2009 at 1:05 PM, Trevor Hemsley  wrote:

>
> I no longer have a RHEL4 system to try it on but our standard until a
> few months ago was RHEL4 and puppetd --test certainly used to work
> (--test includes --no-daemonize)
>
> I seem to remember that we had other problems with Ruby as supplied by
> Centos4 so we installed these:
>
> ruby-1.8.5-5.el4.centos.1.i386.rpm
> ruby-irb-1.8.5-5.el4.centos.1.i386.rpm
> ruby-libs-1.8.5-5.el4.centos.1.i386.rpm
> ruby-mode-1.8.5-5.el4.centos.1.i386.rpm
> ruby-rdoc-1.8.5-5.el4.centos.1.i386.rpm
>
> Didn't see any problems after that.
>
> Derek Yarnell wrote:
> > I spoke too soon, I recompiled with ruby 1.8.7, added rubygems and
> > installed puppet and got the same behavior on RHEL4.
> >
> > Can anyone confirm that --no-daemonize works for them on RHEL4?
> >
> > puppetd --onetime --no-daemonize --verbose --debug
> >
> > Thanks,
> > derek
> >
> > On Thu, Jul 23, 2009 at 7:40 PM, Derek Yarnell
> > mailto:derektyarn...@gmail.com>> wrote:
> >
> > Ok, this would seem to be a problem on RHEL4 w/ the built in ruby
> > as my RHEL5 w/ the built in ruby works as I would expect running
> > the same command.
> >
> > RHEL4 ships with,
> >
> > # ruby --version
> > ruby 1.8.1 (2003-12-25) [i386-linux-gnu]
> >
> > What are other people doing on RHEL4 are you using the built in
> > ruby or are you providing a newer version?  Funny thing is that
> > everything works just fine other than this with the built in ruby,
> > I just wanted to make sure that in the %post install of the
> > kickstart that puppet actually ran (if you background it the %post
> > install will just finish and reboot before puppet has a chance to
> > run).  Anyone else been trying to do this?
> >
> > Thanks,
> > derek
> >
> > On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan
> > mailto:peiriann...@gmail.com>> wrote:
> >
> >
> > Just for input, I haven't been seeing this behavior with
> > 0.24.8 (or
> > any previous release) on Fedora.
> >
> > Trevor
> >
> > On Thu, Jul 23, 2009 at 17:43, Derek
> > Yarnell > > wrote:
> > > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies
> > mailto:l...@madstop.com>> wrote:
> > >>
> > >> It's not daemonizing there, it's exiting -- if you use
> > --onetime, it
> > >> exits after the run.
> > >
> > > It really does daemonize there,
> > > # ps axuww | grep puppet
> > > root  2476  0.0  0.2  4036  644 pts/1S+   17:41
> > 0:00 grep puppet
> > > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
> > > debug: Creating default schedules
> > > debug: Failed to load library 'shadow' for feature 'libshadow'
> > > debug: Failed to load library 'ldap' for feature 'ldap'
> > > ...
> > > debug: Finishing transaction -606656664 with 0 changes
> > > # ps axuww | grep puppet
> > > root  2518 88.0  6.0 19080 15412 ?   Rs   17:41
> > 0:00 /usr/bin/ruby
> > > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
> > > root  2541  0.0  0.2  4888  648 pts/1S+   17:41
> > 0:00 grep puppet
> > > It is doing --onetime correctly but still regardless of putting
> > > --no-daemonize or not it still forks into the background.
> > > --
> > > ---
> > > Derek T. Yarnell
> > >
> > > >
> > >
> >
> >
> >
> >
> >
> > --
> > ---
> > Derek T. Yarnell
> >
> >
> >
> >
> > --
> > ---
> > Derek T. Yarnell
> >
> > >
>
> --
>
> Trevor Hemsley
> Infrastructure Engineer
> .
> * C A L Y P S O
> * Brighton, UK
>
> OFFICE  +44 (0) 1273 666 350
> FAX +44 (0) 1273 666 351
>
> .
> www.calypso.com
>
> This electronic-mail might contain confidential information intended
> only for the use by the entity named. If the reader of this message is
> not the intended recipient, the reader is hereby notified that any
> dissemination, distribution or copying is strictly prohibited.
>
> * P * /*/ Please consider the environment before printing this e-mail /*/
>
>
> >
>


-- 
---
Derek T. Yarnell

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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=e

[Puppet Users] Re: puppetd no-daemonize

[Trevor Hemsley]

I no longer have a RHEL4 system to try it on but our standard until a
few months ago was RHEL4 and puppetd --test certainly used to work
(--test includes --no-daemonize)

I seem to remember that we had other problems with Ruby as supplied by
Centos4 so we installed these:

ruby-1.8.5-5.el4.centos.1.i386.rpm
ruby-irb-1.8.5-5.el4.centos.1.i386.rpm
ruby-libs-1.8.5-5.el4.centos.1.i386.rpm
ruby-mode-1.8.5-5.el4.centos.1.i386.rpm
ruby-rdoc-1.8.5-5.el4.centos.1.i386.rpm

Didn't see any problems after that.

Derek Yarnell wrote:
> I spoke too soon, I recompiled with ruby 1.8.7, added rubygems and
> installed puppet and got the same behavior on RHEL4.
>
> Can anyone confirm that --no-daemonize works for them on RHEL4?
>
> puppetd --onetime --no-daemonize --verbose --debug
>
> Thanks,
> derek
>
> On Thu, Jul 23, 2009 at 7:40 PM, Derek Yarnell
> mailto:derektyarn...@gmail.com>> wrote:
>
> Ok, this would seem to be a problem on RHEL4 w/ the built in ruby
> as my RHEL5 w/ the built in ruby works as I would expect running
> the same command.
>
> RHEL4 ships with,
>
> # ruby --version
> ruby 1.8.1 (2003-12-25) [i386-linux-gnu]
>
> What are other people doing on RHEL4 are you using the built in
> ruby or are you providing a newer version?  Funny thing is that
> everything works just fine other than this with the built in ruby,
> I just wanted to make sure that in the %post install of the
> kickstart that puppet actually ran (if you background it the %post
> install will just finish and reboot before puppet has a chance to
> run).  Anyone else been trying to do this?
>
> Thanks,
> derek
>
> On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan
> mailto:peiriann...@gmail.com>> wrote:
>
>
> Just for input, I haven't been seeing this behavior with
> 0.24.8 (or
> any previous release) on Fedora.
>
> Trevor
>
> On Thu, Jul 23, 2009 at 17:43, Derek
> Yarnell > wrote:
> > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies
> mailto:l...@madstop.com>> wrote:
> >>
> >> It's not daemonizing there, it's exiting -- if you use
> --onetime, it
> >> exits after the run.
> >
> > It really does daemonize there,
> > # ps axuww | grep puppet
> > root  2476  0.0  0.2  4036  644 pts/1S+   17:41  
> 0:00 grep puppet
> > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
> > debug: Creating default schedules
> > debug: Failed to load library 'shadow' for feature 'libshadow'
> > debug: Failed to load library 'ldap' for feature 'ldap'
> > ...
> > debug: Finishing transaction -606656664 with 0 changes
> > # ps axuww | grep puppet
> > root  2518 88.0  6.0 19080 15412 ?   Rs   17:41  
> 0:00 /usr/bin/ruby
> > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
> > root  2541  0.0  0.2  4888  648 pts/1S+   17:41  
> 0:00 grep puppet
> > It is doing --onetime correctly but still regardless of putting
> > --no-daemonize or not it still forks into the background.
> > --
> > ---
> > Derek T. Yarnell
> >
> > >
> >
>
>
>
>
>
> -- 
> ---
> Derek T. Yarnell
>
>
>
>
> -- 
> ---
> Derek T. Yarnell
>
> >

-- 

Trevor Hemsley
Infrastructure Engineer
.
* C A L Y P S O
* Brighton, UK   

OFFICE  +44 (0) 1273 666 350
FAX +44 (0) 1273 666 351

.
www.calypso.com

This electronic-mail might contain confidential information intended
only for the use by the entity named. If the reader of this message is
not the intended recipient, the reader is hereby notified that any
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: uninstall package on ubuntu

[Wes Reneau]

 The puppetmaster was still on 8.04.  Upgrading to 9.04 hopefully solve my
problems.

How stupid of me.

On Fri, Jul 24, 2009 at 12:25 PM, Wes Reneau  wrote:

> Replied in line, blue.
>
> On Fri, Jul 24, 2009 at 11:10 AM, Udo Waechter <
> udo.waech...@uni-osnabrueck.de> wrote:
>
>> Hi,
>> several problems:
>> On 24.07.2009, at 16:52, Wes Reneau wrote:
>>
>>  Ubuntu 9.04 (Juanty) Server and Client run Jaunty
>>> Puppetmaster 0.24.4-3
>>> Puppet (client)0.24.5-3
>>>
>>>  Usually you should not run newer puppet-clients againts older
>> puppet-master. The other way round usually works.
>>
> Client and Server were both installed from default REPO's.
>
> If Jaunty has different version for master/client, this is a bug with
> ubuntu and should be filed there.
> I'll look into this.
>
>>
>> As a off-topic side note: The most recent version of Ubuntu (not LTS)
>> usually has problems... for production environments we have the rule to be
>> one non-LTS version behind.
>
> Funny you mention this, I argued the same point when everyone wanted to
> jump on Jaunty.  I prefer the LTS versions, knowing that some things will be
> forever broken until you upgrade distros.
>
>>
>>
>>  sudo puppetd --verbose
>>> err: Could not create PID file: /var/run/puppet/puppetd.pid
>>>
>> Yep, this is a problem. does /var/run/puppet exist?
>
> It exists.
>
>>
>>
>> udo.
>>
>>
>> --
>> :: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
>> :: genuine input for your ears: http://auriculabovinari.de
>> ::  your eyes: http://ezag.zoide.net
>> ::  your brain: http://zoide.net
>>
>>
>>
>>
>>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd no-daemonize

[Derek Yarnell]

I spoke too soon, I recompiled with ruby 1.8.7, added rubygems and installed
puppet and got the same behavior on RHEL4.
Can anyone confirm that --no-daemonize works for them on RHEL4?

puppetd --onetime --no-daemonize --verbose --debug

Thanks,
derek

On Thu, Jul 23, 2009 at 7:40 PM, Derek Yarnell wrote:

> Ok, this would seem to be a problem on RHEL4 w/ the built in ruby as my
> RHEL5 w/ the built in ruby works as I would expect running the same command.
> RHEL4 ships with,
>
> # ruby --version
> ruby 1.8.1 (2003-12-25) [i386-linux-gnu]
>
> What are other people doing on RHEL4 are you using the built in ruby or are
> you providing a newer version?  Funny thing is that everything works just
> fine other than this with the built in ruby, I just wanted to make sure that
> in the %post install of the kickstart that puppet actually ran (if you
> background it the %post install will just finish and reboot before puppet
> has a chance to run).  Anyone else been trying to do this?
>
> Thanks,
> derek
>
> On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan wrote:
>
>>
>> Just for input, I haven't been seeing this behavior with 0.24.8 (or
>> any previous release) on Fedora.
>>
>> Trevor
>>
>> On Thu, Jul 23, 2009 at 17:43, Derek Yarnell
>> wrote:
>> > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies  wrote:
>> >>
>> >> It's not daemonizing there, it's exiting -- if you use --onetime, it
>> >> exits after the run.
>> >
>> > It really does daemonize there,
>> > # ps axuww | grep puppet
>> > root  2476  0.0  0.2  4036  644 pts/1S+   17:41   0:00 grep
>> puppet
>> > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
>> > debug: Creating default schedules
>> > debug: Failed to load library 'shadow' for feature 'libshadow'
>> > debug: Failed to load library 'ldap' for feature 'ldap'
>> > ...
>> > debug: Finishing transaction -606656664 with 0 changes
>> > # ps axuww | grep puppet
>> > root  2518 88.0  6.0 19080 15412 ?   Rs   17:41   0:00
>> /usr/bin/ruby
>> > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug
>> > root  2541  0.0  0.2  4888  648 pts/1S+   17:41   0:00 grep
>> puppet
>> > It is doing --onetime correctly but still regardless of putting
>> > --no-daemonize or not it still forks into the background.
>> > --
>> > ---
>> > Derek T. Yarnell
>> >
>> > >
>> >
>>
>> >>
>>
>
>
> --
> ---
> Derek T. Yarnell
>



-- 
---
Derek T. Yarnell

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: uninstall package on ubuntu

[Wes Reneau]

Replied in line, blue.

On Fri, Jul 24, 2009 at 11:10 AM, Udo Waechter <
udo.waech...@uni-osnabrueck.de> wrote:

> Hi,
> several problems:
> On 24.07.2009, at 16:52, Wes Reneau wrote:
>
>  Ubuntu 9.04 (Juanty) Server and Client run Jaunty
>> Puppetmaster 0.24.4-3
>> Puppet (client)0.24.5-3
>>
>>  Usually you should not run newer puppet-clients againts older
> puppet-master. The other way round usually works.
>
Client and Server were both installed from default REPO's.

If Jaunty has different version for master/client, this is a bug with ubuntu
and should be filed there.
I'll look into this.

>
> As a off-topic side note: The most recent version of Ubuntu (not LTS)
> usually has problems... for production environments we have the rule to be
> one non-LTS version behind.

Funny you mention this, I argued the same point when everyone wanted to jump
on Jaunty.  I prefer the LTS versions, knowing that some things will be
forever broken until you upgrade distros.

>
>
>  sudo puppetd --verbose
>> err: Could not create PID file: /var/run/puppet/puppetd.pid
>>
> Yep, this is a problem. does /var/run/puppet exist?

It exists.

>
>
> udo.
>
>
> --
> :: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
> :: genuine input for your ears: http://auriculabovinari.de
> ::  your eyes: http://ezag.zoide.net
> ::  your brain: http://zoide.net
>
>
>
>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: uninstall package on ubuntu

[Udo Waechter]

Hi,
several problems:
On 24.07.2009, at 16:52, Wes Reneau wrote:


Ubuntu 9.04 (Juanty) Server and Client run Jaunty
Puppetmaster 0.24.4-3
Puppet (client)0.24.5-3

Usually you should not run newer puppet-clients againts older puppet- 
master. The other way round usually works.


If Jaunty has different version for master/client, this is a bug with  
ubuntu and should be filed there.


As a off-topic side note: The most recent version of Ubuntu (not LTS)  
usually has problems... for production environments we have the rule  
to be one non-LTS version behind.



sudo puppetd --verbose
err: Could not create PID file: /var/run/puppet/puppetd.pid

Yep, this is a problem. does /var/run/puppet exist?

udo.

--
:: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
:: genuine input for your ears: http://auriculabovinari.de
::  your eyes: http://ezag.zoide.net
::  your brain: http://zoide.net






smime.p7s
Description: S/MIME cryptographic signature

[Puppet Users] Re: uninstall package on ubuntu

[Wes Reneau]

Ubuntu 9.04 (Juanty) Server and Client run Jaunty
Puppetmaster 0.24.4-3
Puppet (client)0.24.5-3

sudo puppetd --verbose
err: Could not create PID file: /var/run/puppet/puppetd.pid


Seems that I have underlying problems.




On Fri, Jul 24, 2009 at 10:38 AM, Udo Waechter <
udo.waech...@uni-osnabrueck.de> wrote:

> Hi.
>
> This is really strange and should not be.
> We use ubuntu (hardy/intrepid) a lot and package management with puppet
> works really well.
>
> What ubuntu version and what puppet version?
>
> What happens if you user --verbose for puppetd? That should show you a
> message about the Package["vlc"]
> What happens if you manually uninstall vlc "aptitude remove vlc"? Some
> packages have strange dependencies that are first removed and then installed
> again if another package that depends on those should be installed (via
> puppet).
>
> We use puppet 0.24.8 (from debian/unstable) and puppetmaster 0.24.8, but in
> all previous versions (since 0.22) we never had such problems with apt/dpkg
> based Linux-boxes.
>
> bye.
> udo
>
>
> On 24.07.2009, at 15:52, Wes Reneau wrote:
>
>  So, back to my original question, how would I purge vlc and the other
>> dependencies that are installed as a result of the original recipe?
>>
>> Thanks
>>
>>
>> On Thu, Jul 23, 2009 at 8:12 PM, Scott Smith  wrote:
>>
>> Avi Miller wrote:
>> > Scott Smith wrote:
>> >> Am fairly certain --test implies --dry-run and won't actually enact
>> >> any changes.
>> >
>> > Sorry, but --test certainly does apply changes. We use it a lot!
>> >
>>
>> D'oh, I misread. That's what  I get for reading E-mail on my iphone
>> while riding the bus :(
>>
>> -scott
>>
>>
>>
>>
>> >>
>>
> --
> :: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
> :: genuine input for your ears: http://auriculabovinari.de
> ::  your eyes: http://ezag.zoide.net
> ::  your brain: http://zoide.net
>
>
>
>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: uninstall package on ubuntu

[Udo Waechter]

Hi.

This is really strange and should not be.
We use ubuntu (hardy/intrepid) a lot and package management with  
puppet works really well.


What ubuntu version and what puppet version?

What happens if you user --verbose for puppetd? That should show you a  
message about the Package["vlc"]
What happens if you manually uninstall vlc "aptitude remove vlc"? Some  
packages have strange dependencies that are first removed and then  
installed again if another package that depends on those should be  
installed (via puppet).


We use puppet 0.24.8 (from debian/unstable) and puppetmaster 0.24.8,  
but in all previous versions (since 0.22) we never had such problems  
with apt/dpkg based Linux-boxes.


bye.
udo

On 24.07.2009, at 15:52, Wes Reneau wrote:

So, back to my original question, how would I purge vlc and the  
other dependencies that are installed as a result of the original  
recipe?


Thanks


On Thu, Jul 23, 2009 at 8:12 PM, Scott Smith  wrote:

Avi Miller wrote:
> Scott Smith wrote:
>> Am fairly certain --test implies --dry-run and won't actually enact
>> any changes.
>
> Sorry, but --test certainly does apply changes. We use it a lot!
>

D'oh, I misread. That's what  I get for reading E-mail on my iphone
while riding the bus :(

-scott




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google  
Groups "Puppet Users" group.

To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---



--
:: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
:: genuine input for your ears: http://auriculabovinari.de
::  your eyes: http://ezag.zoide.net
::  your brain: http://zoide.net






smime.p7s
Description: S/MIME cryptographic signature

[Puppet Users] Re: uninstall package on ubuntu

[Wes Reneau]

So, back to my original question, how would I purge vlc and the other
dependencies that are installed as a result of the original recipe?

Thanks


On Thu, Jul 23, 2009 at 8:12 PM, Scott Smith  wrote:

>
> Avi Miller wrote:
> > Scott Smith wrote:
> >> Am fairly certain --test implies --dry-run and won't actually enact
> >> any changes.
> >
> > Sorry, but --test certainly does apply changes. We use it a lot!
> >
>
> D'oh, I misread. That's what  I get for reading E-mail on my iphone
> while riding the bus :(
>
> -scott
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: class dependencies

[jcbollinger]

On Jul 23, 11:17 pm, Greg  wrote:
> Simple answer - no. Dependencies can only be between objects in
> 0.24.x...

For what it's worth, this is reputed to be a new feature of Puppet
0.25, which release is currently in beta testing.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Solaris SMF services and their dependencies...

[Matthew Hyclak]

On Thu, Jul 23, 2009 at 11:33 PM, Greg wrote:
>
> Hi all,
>
> I have an NFS server on our network sharing out package files for
> Puppet to install to all and sundry. The clients access said NFS
> server via an automounter configuration (I don't want the packages
> share mounted all the time, only when installing packages) As a
> result, installation of packages depends on autofs... So I have the
> following:
>
> service { "autofs": ensure => running", subscribe => File["/etc/
> auto_master"] }
>
> package { "SUNWfoo":
>  # Yes, I'm using /net - its evil, I know...
>  source => "/net/$installsvr/export/pkgs/$kernelrelease/$hardwareisa/
> SUNWfoo.pkg",
>  require => Service["autofs"]
> }
>
> I'm serving it out this way for a number of reasons, including slow
> Puppet fileserving for large files, inability to specify response
> files with http package streams on Solaris' package management system
> - and so on...
>
> The problem I have is that if the autofs service is restarted right
> before a package is installed (which typically happens when I do a
> jumpstart as I put in a new /etc/auto_master) then the service is
> still restarting whilst the subsequent resources are being configured.
> So the package installs fail because they can't see the files.
>
> 5 seconds later the automounter comes online and the files are
> available...
>
> Basically the problem here is that the command used to restart the
> service doesn't wait for the service to actually restart - it just
> triggers the SMF services to restart it. I can't see any options in
> svcadm to restart and wait for it to be online again - which is a
> little annoying. And I think Puppet makes the assumption that because
> it told the service to restart that it has actually done that...
>
> If I take the requirement for autofs out from the packages - nothing
> installs as it tries to install packages too early and the system
> isn't configured enough to retrieve them...
>
> Has anyone else seen this condition happen? If so, what did you do to
> work around (or preferably fix) the problem?
>

You can specify the restart command for a service, so I would just use
your own for autofs that includes a "&& sleep 5" after the regular
restart command.

Matt

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Tidy symlinks

[Trevor Vaughan]

This has turned into a bit of an interesting adventure in the syntax of Tidy.

Environment: puppet 0.24.8 on Fedora Core 11

After each run, I touch /tmp/foodir/bar to have something to tidy.

Test code:

# Environment Setup
$testdir = "/tmp/foodir"
$subdir = "$testdir/subdir"

file { "$testdir":
ensure => 'directory',
require => Tidy["$testdir"]
}

file { "$subdir":
ensure => 'directory'
}

file { "$subdir/foo":
ensure => 'file',
content => "foo"
}

file { "$testdir/foolink":
ensure => "$subdir/foo"
}

Test 1:

tidy { "$testdir":
age => '0s',
matches => "*"
}

Test 1 Result: Fail, bar remains

Test 2:

tidy { "$testdir":
   age => '0s',
   matches => ".*"
}

Test 2 Result: Fail, bar remains

Test 3:

tidy { "$testdir":
age => '0s',
recurse => 'true'
}

Test 3 Result: Pass, bar deleted

Test 4:

Created a symlink /tmp/foodir/baz that points to /tmp/foodir/subdir/foo

tidy { "$testdir":
age => '0s',
recurse => 'true'
}

Test 4 Result: Partial, bar deleted, baz remains

Test 5:

Created the symlink baz and touched bar

tidy { "$testdir":
   age => '0s',
   recurse => 'true',
   type => 'mtime'
}

Test 5 Result: Pass

Comments:

I don't quite understand why the pass/fail combinations work above.  I
also noticed that any subdirectory that is explicitly managed will not
be recursed into even if recurse is set to 'true'.  I believe that it
should recurse through all subdirectories, not just the ones that
aren't otherwise managed.

Thanks,

Trevor


On Fri, Jul 24, 2009 at 00:21, Greg wrote:
>
> Trevor,
>
> Not sure - the docs don't seem to reference symlinks in terms of
> tidy...
>
> Just something to try - does setting rmdirs => true make any
> difference?
>
> Greg
>
> On Jul 24, 11:19 am, Trevor Vaughan  wrote:
>> So, I have a directory of symlinks that I'm managing and Tidy doesn't
>> seem to be doing much for me in there.
>>
>> Does Tidy ignore symlinks for some reason?
>>
>> If not, does anyone have the correct syntax?
>>
>> Thanks,
>>
>> Trevor
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: passenger vs mongrel performance

[Larry Ludwig]

Ohad,

Now that we know that passenger is configured in Mark's case, try  
rubyEE and let us know the result.

-L

--
Larry Ludwig
Reductive Labs


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: passenger vs mongrel performance

[Mark Plaksin]

Ohad Levy  writes:

> Hi All,
>
> I've recently upgraded all of my mongrels to passenger on all of my
> puppetmasters, and I'm seeing some performance degradations, hopefully
> someone can provide some feedback..
>
> i see an increase in cpu and load indicators, and i've calculated that the
> actual puppet compile time has increased:
> using mongrels
>  - AVG of 3.24515 seconds, out of 30897 config runs
> using passenger
> AVG of 3.53524 seconds, out of 5992 config runs

Once we got our Passenger config options in the right place our compile
time went down by about *2/3*!  Our CPU user stats seem to have gone up
a teensy bit but overall load average is about the same.

To complicate matters (or kill two birds with one stone :), when we
switched to Passenger we also switched to RubyEE.

> the passenger option that i use are:
> PassengerMaxPoolSize 15
> PassengerMaxRequests 3000
> PassengerStatThrottleRate 600

FWIW, here are our options:

PassengerHighPerformance on
PassengerMaxPoolSize 24
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RackAutoDetect Off
RailsAutoDetect Off

We were running 10 puppetmasterds with Mongrel.  With Passenger we
usually see 6-8 running.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Adding users to multiple groups

[Bryan Ross]

> Try using: ingroups => ['wheel', 'devel']

I was hoping to keep my users organised in neat classes as per the
Best Practices documentation, rather than have to define all the
groups a specific user is in all in a single place.  However, as you
point out, it is a valid work around.

I presume 'ingroups' is just an alias for 'groups'?  Its not mentioned
in the Type Reference documentation, but I tried it, and it seems to
display the same functionality as the 'groups' property.

Generally speaking, am I thinking about the '+>' in the right way?  If
you cant update and add to properties of virtual resources, then I'm
struggling to find a use for it?  Or, do I need to perhaps need to add
a dependency to ensure that I realize() my virtual resource after I've
changed its properties?

Cheers,
Bryan

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~--~~~~--~~--~--~---