Puppet users - Jan 2009 - Setting ownership or mode of files created by nagios types

So I don''t know what happened to the other thread, but all I want to
do is be able to set the owner or the mode of the files written by all
the nagios types, the default is root ownership with a mode of 600
which, for ubuntu, completely breaks nagios.  There has to be a way to
do this when the files are written instead of after.

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

I''d really appreciate some help with this, I''ve tried to find
the
answer in the source code but I haven''t had much luck finding an
answer.  Is there really no one that uses the built in nagios
resources?

Scott

On Jan 31, 8:09 am, Scott <scott...@gmail.com>
wrote:
> So I don''t know what happened to the other thread, but all I want
to
> do is be able to set the owner or the mode of the files written by all
> the nagios types, the default is root ownership with a mode of 600
> which, for ubuntu, completely breaks nagios.  There has to be a way to
> do this when the files are written instead of after.
>
> Cheers,
> 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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi
> I''d really appreciate some help with this, I''ve tried to
find the
> answer in the source code but I haven''t had much luck finding an
> answer.  Is there really no one that uses the built in nagios
> resources?
I do and as mentioned before, use a wrapper define which takes care of  
the file modes.

As you have somehow to set the target attribute of the nagios  
resource, as in your setup every host gets into its own file, you can  
use the same path for a file definition and manage the modes there.

Why nagios resources can''t handle file modes? Because nagios resources
don''t manage a file, they manage the nagios entry within a file.
You would have various problems: What if multiple nagios resouces  
point to the same file but would have different file modes? Again it''s
not the task of nagios resources to manage the file.

cheers pete

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Use a default acl that gives nagios user and nagios group access to the 
whole nagios tree.

Peter Meier wrote:
> Hi
>
>   
>> I''d really appreciate some help with this, I''ve tried
to find the
>> answer in the source code but I haven''t had much luck finding
an
>> answer.  Is there really no one that uses the built in nagios
>> resources?
>>     
>
> I do and as mentioned before, use a wrapper define which takes care of  
> the file modes.
>
> As you have somehow to set the target attribute of the nagios  
> resource, as in your setup every host gets into its own file, you can  
> use the same path for a file definition and manage the modes there.
>
> Why nagios resources can''t handle file modes? Because nagios
resources
> don''t manage a file, they manage the nagios entry within a file.
> You would have various problems: What if multiple nagios resouces  
> point to the same file but would have different file modes? Again
it''s
> not the task of nagios resources to manage the file.
>
> cheers pete
>
> >
>   

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Scott, I''m curious, did you try what I said? All it takes is enabling 
the ''acl'' fsopt, remounting the volume, and adding a default
FACL to
your nagios root.

Scott wrote:
> So I don''t know what happened to the other thread, but all I want
to
> do is be able to set the owner or the mode of the files written by all
> the nagios types, the default is root ownership with a mode of 600
> which, for ubuntu, completely breaks nagios.  There has to be a way to
> do this when the files are written instead of after.
>
> Cheers,
> 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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---