Puppet users - Jul 2010 - manage_internal_file_permissions, /etc/sysconfig, and/or command line startup...

Okay, maybe I''m being dense...but I''m missing something here.

First off, using puppet 2.6 on centos 5.5.

I want to store /etc/puppet and /var/lib/puppet elsewhere...but have
symbolic links for /etc/puppet and /var/lib/puppet that point to the
actual directories.  Puppet obviously rewrites those symlinks when I
start it up.

So I read, and saw "manage_internal_file_permissions" - looks like
just what I want.  But setting it in /etc/puppet/puppet.conf isn''t
working - it''s rewritten before it''s checked.

So then I tried setting it on the command line by editing /etc/
sysconfig/puppetmaster and setting PUPPETMASTER_EXTRA_OPTS to "--
manage_internal_file_permissions false", but that''s not working. 
So I
also tried setting it to "--no-manage_internal_file_permissions", but
that''s not working either.

What the heck am I doing wrong?

Thanks-

Tom

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Try using a bind mount instead of symlink

Sent from my iPhone

On Jul 27, 2010, at 6:48 PM, Tom <thomas.a.johnson@gmail.com> wrote:
> Okay, maybe I''m being dense...but I''m missing something
here.
> 
> First off, using puppet 2.6 on centos 5.5.
> 
> I want to store /etc/puppet and /var/lib/puppet elsewhere...but have
> symbolic links for /etc/puppet and /var/lib/puppet that point to the
> actual directories.  Puppet obviously rewrites those symlinks when I
> start it up.
> 
> So I read, and saw "manage_internal_file_permissions" - looks
like
> just what I want.  But setting it in /etc/puppet/puppet.conf isn''t
> working - it''s rewritten before it''s checked.
> 
> So then I tried setting it on the command line by editing /etc/
> sysconfig/puppetmaster and setting PUPPETMASTER_EXTRA_OPTS to "--
> manage_internal_file_permissions false", but that''s not
working.  So I
> also tried setting it to "--no-manage_internal_file_permissions",
but
> that''s not working either.
> 
> What the heck am I doing wrong?
> 
> Thanks-
> 
> Tom
> 
> -- 
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

This is actually what I''ve done, temporarily, so I can move forward
with implementing puppet....

but I''d love to know what else I''m doing wrong, if anyone can
tell me.

Why don''t the command line options work? Is my syntax wrong?


-t
On Jul 28, 4:48 am, Christopher Johnston <chjoh...@gmail.com>
wrote:
> Try using a bind mount instead of symlink
>
> Sent from my iPhone
>
> On Jul 27, 2010, at 6:48 PM, Tom <thomas.a.john...@gmail.com> wrote:
>
>
>
> > Okay, maybe I''m being dense...but I''m missing
something here.
>
> > First off, using puppet 2.6 on centos 5.5.
>
> > I want to store /etc/puppet and /var/lib/puppet elsewhere...but have
> > symbolic links for /etc/puppet and /var/lib/puppet that point to the
> > actual directories.  Puppet obviously rewrites those symlinks when I
> > start it up.
>
> > So I read, and saw "manage_internal_file_permissions" -
looks like
> > just what I want.  But setting it in /etc/puppet/puppet.conf
isn''t
> > working - it''s rewritten before it''s checked.
>
> > So then I tried setting it on the command line by editing /etc/
> > sysconfig/puppetmaster and setting PUPPETMASTER_EXTRA_OPTS to "--
> > manage_internal_file_permissions false", but that''s not
working.  So I
> > also tried setting it to
"--no-manage_internal_file_permissions", but
> > that''s not working either.
>
> > What the heck am I doing wrong?
>
> > Thanks-
>
> > Tom
>
> > --
> > 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+unsubscribe@googlegroups.com.
> > For more options, visit this group
athttp://groups.google.com/group/puppet-users?hl=en.
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wed, Jul 28, 2010 at 12:45 PM, Tom <thomas.a.johnson@gmail.com>
wrote:
> This is actually what I''ve done, temporarily, so I can move
forward
> with implementing puppet....
>
> but I''d love to know what else I''m doing wrong, if anyone
can tell me.
>
> Why don''t the command line options work? Is my syntax wrong?
This is issue #650 in puppet, you''re not doing anything wrong.

http://projects.puppetlabs.com/issues/650

The work around is to use a bind mount as you''ve done.

Cheers,
-- 
Jeff McCune
http://www.puppetlabs.com/

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I saw this bug but the final comment in there said:

"Note that you can set ‘manage_internal_file_permissions’ to false to
disable this behaviour."

So that''s what I was trying to do - use
"manage_internal_file_permissions" to disable it.  But that
doesn''t
seem to work either, does it?  You can''t use this from the command
line, can you?




On Jul 28, 1:59 pm, Jeff McCune <j...@puppetlabs.com>
wrote:
> On Wed, Jul 28, 2010 at 12:45 PM, Tom <thomas.a.john...@gmail.com>
wrote:
> > This is actually what I''ve done, temporarily, so I can move
forward
> > with implementing puppet....
>
> > but I''d love to know what else I''m doing wrong, if
anyone can tell me.
>
> > Why don''t the command line options work? Is my syntax wrong?
>
> This is issue #650 in puppet, you''re not doing anything wrong.
>
> http://projects.puppetlabs.com/issues/650
>
> The work around is to use a bind mount as you''ve done.
>
> Cheers,
> --
> Jeff McCunehttp://www.puppetlabs.com/
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wed, 28 Jul 2010, Tom wrote:
> "Note that you can set =??manage_internal_file_permissions=?? to false
to
> disable this behaviour."
> 
> So that''s what I was trying to do - use
> "manage_internal_file_permissions" to disable it.  But that
doesn''t
> seem to work either, does it?  You can''t use this from the command
> line, can you?
The command-line equivalent would be
"--no-manage_internal_file_permissions".
Be careful with the hyphens and underlines.

--apb (Alan Barrett)

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

That''s what I thought, but it doesn''t work.  So
there''s nothing wrong
with what I''m doing?  Perhaps I should file a bug report...


Centos 5.5, Puppet 2.6:


# ls -ld /etc/puppet
lrwxrwxrwx 1 root root 21 Jul 29 17:56 /etc/puppet -> /usr/local/etc/
puppet
# ls -ld /var/lib/puppet
lrwxrwxrwx 1 root root 36 Jul 29 17:56 /var/lib/puppet -> /usr/local/
etc/puppet/var/lib/puppet


# puppetmasterd --no-manage_internal_file_permissions


# ls -ld /etc/puppet
drwxr-xr-x 4 root root 4096 Jul 29 17:57 /etc/puppet
# ls -ld /var/lib/puppet
drwxr-xr-x 12 root root 4096 Jul 29 17:57 /var/lib/puppet





On Jul 29, 3:26 am, Alan Barrett <a...@cequrux.com>
wrote:
> On Wed, 28 Jul 2010, Tom wrote:
> > "Note that you can set =??manage_internal_file_permissions=?? to
false to
> > disable this behaviour."
>
> > So that''s what I was trying to do - use
> > "manage_internal_file_permissions" to disable it.  But that
doesn''t
> > seem to work either, does it?  You can''t use this from the
command
> > line, can you?
>
> The command-line equivalent would be
> "--no-manage_internal_file_permissions".
> Be careful with the hyphens and underlines.
>
> --apb (Alan Barrett)
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Maybe I am missing one of your requirements, but I keep my puppet
master files somewhere other than /etc/puppet and /var/lib/puppet, and
I just use the --confdir option to puppetmasterd.

$ grep PUPPETMASTER_EXTRA_OPTS /etc/sysconfig/puppetmaster
PUPPETMASTER_EXTRA_OPTS="--confdir /tr01/puppet"


- Chad

On Thu, Jul 29, 2010 at 1:57 PM, Tom <thomas.a.johnson@gmail.com>
wrote:
> That''s what I thought, but it doesn''t work.  So
there''s nothing wrong
> with what I''m doing?  Perhaps I should file a bug report...
>
>
> Centos 5.5, Puppet 2.6:
>
>
> # ls -ld /etc/puppet
> lrwxrwxrwx 1 root root 21 Jul 29 17:56 /etc/puppet -> /usr/local/etc/
> puppet
> # ls -ld /var/lib/puppet
> lrwxrwxrwx 1 root root 36 Jul 29 17:56 /var/lib/puppet -> /usr/local/
> etc/puppet/var/lib/puppet
>
>
> # puppetmasterd --no-manage_internal_file_permissions
>
>
> # ls -ld /etc/puppet
> drwxr-xr-x 4 root root 4096 Jul 29 17:57 /etc/puppet
> # ls -ld /var/lib/puppet
> drwxr-xr-x 12 root root 4096 Jul 29 17:57 /var/lib/puppet
>
>
>
>
>
> On Jul 29, 3:26 am, Alan Barrett <a...@cequrux.com> wrote:
>> On Wed, 28 Jul 2010, Tom wrote:
>> > "Note that you can set =??manage_internal_file_permissions=??
to false to
>> > disable this behaviour."
>>
>> > So that''s what I was trying to do - use
>> > "manage_internal_file_permissions" to disable it.  But
that doesn''t
>> > seem to work either, does it?  You can''t use this from
the command
>> > line, can you?
>>
>> The command-line equivalent would be
>> "--no-manage_internal_file_permissions".
>> Be careful with the hyphens and underlines.
>>
>> --apb (Alan Barrett)
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Chad M. Huneycutt

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.