oup, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
Welcome to Puppet Labs Dawn!
--
Kelsey Hightower
Operations Manager
Puppet Labs
(678) 4719501
--
You received this messag
On Tuesday, May 8, 2012 7:17:33 PM UTC-4, Andy Parker wrote:
>
> I'll chime in on this now, I suppose.
>
> You are right that both read and write operations are good for
> abstraction. The problem comes that comes into play is that read and write
> operations usually end up with completely differ
have an save API
> >
> > On Tue, May 1, 2012 at 09:31, Kelsey Hightower
> > wrote:
> >
> > > I'm thinking of adding a new save API to Hiera. The idea is that
> > > Hiera
> > > should provide an iterface for saving data, which sh
On Tuesday, May 1, 2012 1:17:53 PM UTC-4, Daniel Pittman wrote:
>
> On Tue, May 1, 2012 at 09:31, Kelsey Hightower
> wrote:
>
> > I'm thinking of adding a new save API to Hiera. The idea is that Hiera
> > should provide an iterface for saving data, which should m
I'm thinking of adding a new save API to Hiera. The idea is that Hiera
should provide an iterface for saving data, which should make it easy for
front-end tools to interact with backends that support saving data.
An example of how this might work is shown in the commit message in the
following
Sent from my iPhone
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options
Right now the way the patch works is that root will create the file
and chown it to what ever user is specified when using the
ssh_authorized_key type. If you want the key to be owned by root, just
specify root as the user.
--
You received this message because you are subscribed to the Google Gro
One use case where it may not be desirable to have users own the keys
is in centralized ssh key setups backed by LDAP and PAM
authentication. In this specific case all keys are stored in a central
location such as /etc/ssh-public-keys/*.pub. The keys are only read by
PAM (root) during the authentic
> I have not taken the time to look, in detail, at this yet, but we
> should consider at least the greater scope of changes that were made
> in that commit before we absorb this.
>
> Daniel
Yeah, I should have searched the repo for previous commits, good
catch.
--
You received this message becau
esults
returned from searching '/proc/self/mountinfo'.
Signed-off-by: Kelsey Hightower
---
Local-branch: ticket/master/8964
lib/facter/selinux.rb | 109 +++-
1 files changed, 61 insertions(+), 48 deletions(-)
diff --git a/lib/facter/selinux.
Cool, now I can remove the work around.
On Jul 13, 4:00 pm, Todd Zullinger wrote:
> Kelsey Hightower wrote:
> > Basically you will need to replace '$releasever' with '5'. With the
> > RHEL 5 release RedHat resolve's $releasever = 5Server.
>
> >
For RHEL 5 you will have to make the following change in puppet.repo:
- baseurl=http://tmz.fedorapeople.org/repo/puppet/epel/$releasever/
$basearch
to
- baseurl=http://tmz.fedorapeople.org/repo/puppet/epel/5/$basearch
Basically you will need to replace '$releasever' with '5'. With the
RHEL 5 rel
On May 26, 11:38 pm, Luke Kanies wrote:
> On May 22, 2009, at 10:26 PM, Kelsey Hightower wrote:
>
>
>
>
>
>
>
> > Puppet::Type.newtype(:tcpwrapper) do
> > �...@doc = "Manages tcpwarppers hosts.allow and hosts.deny entries.
> > The entry will b
tion?
On May 23, 7:43 pm, Sam Rowe wrote:
> On Fri, May 22, 2009 at 11:26 PM, Kelsey Hightower
>
> wrote:
>
> > Puppet::Type.newtype(:tcpwrapper) do
> > �...@doc = "Manages tcpwarppers hosts.allow and hosts.deny entries.
> > The entry will be placed in /etc
I would like to join the call.
On May 19, 11:18 pm, Luke Kanies wrote:
> Or whatever. We probably haven't had quite that many.
>
> Anyway, it's way time for another dev call. The primary topics of
> this call will be Puppet 0.25 and the path to Facter 2.0.
>
> I propose next Wednesday, May 2
Puppet::Type.newtype(:tcpwrapper) do
@doc = "Manages tcpwarppers hosts.allow and hosts.deny entries.
The entry will be placed in /etc/host.allow when 'allow => true'
or 'deny => false'
The entry will be placed in /etc/host.deny when 'deny => true' or
'allow => false'
Default action
What is the next step in order to get this merged into master?
On Apr 25, 8:32 pm, Luke Kanies wrote:
> No idea here, seems ok to me but I wouldn't know.
>
> On Apr 20, 2009, at 6:22 AM, Kelsey Hightower wrote:
>
>
>
>
>
>
>
> > Signed-off-by: Kelsey Hig
Signed-off-by: Kelsey Hightower
---
conf/redhat/logrotate |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/conf/redhat/logrotate b/conf/redhat/logrotate
index e336d60..554d6d1 100644
--- a/conf/redhat/logrotate
+++ b/conf/redhat/logrotate
@@ -1,6 +1,7 @@
/var/log/puppet
Signed-off-by: Kelsey Hightower
---
conf/redhat/logrotate |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/conf/redhat/logrotate b/conf/redhat/logrotate
index e336d60..554d6d1 100644
--- a/conf/redhat/logrotate
+++ b/conf/redhat/logrotate
@@ -1,6 +1,7 @@
/var/log/puppet
19 matches
Mail list logo
