[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: owner and group in files and copy
From: |
Mark . Burgess |
Subject: |
Re: owner and group in files and copy |
Date: |
Thu, 7 Oct 2004 19:13:04 +0200 (MEST) |
There should be no difference between 2.1.9 and 2.1.10, but I shall try
to get around to checking this out.
M
On 7 Oct, Ed Brown wrote:
> I was using 2.1.9 for the test, and am fairly sure that 2.1.6 behaves
> the same as well. Maybe something changed in 2.1.10?
>
>
> On Thu, 2004-10-07 at 09:27, Christian Pearce wrote:
>> hmm... It was definitely happening to me. What version do you run? I
>> am using 2.1.10. I am trying to reproduce it on a smaller snippet of
>> code. I was pulling files from the Cfengine server. Take a look at the
>> code though. It does save the uid and gid.
>>
>> On Thu, 2004-10-07 at 10:13, Ed Brown wrote:
>> > In my experience, and in a test just now, setting destination ownership
>> > for one copy statement does not carry over to subsequent copy
>> > statements. The default behavior in the absence of explicit settings is
>> > to preserve the ownership of the source file.
>> >
>> > -Ed
>> >
>> >
>> > On Wed, 2004-10-06 at 19:00, Chris Edillon wrote:
>> > > On Wed, 2004-10-06 at 13:17, Christian Pearce wrote:
>> > > > Why does the owner or group get carried over to the next copy statement
>> > > > executed? I briefly looked at the code, it looks like it saves the uid
>> > > > and gid. So it was intentionally as far as I can tell.
>> > > >
>> > > > I can't for the life of my figure out why we would want this. I am
>> > > > going to be forced to explicitly set ownership for every copy statement
>> > > > I have. Geehz! Can someone explain why this is here?
>> > > >
>> > > i would think that if it wasn't there, you would be
>> > > forced to explicitly set ownership for every copy statement
>> > > anyway (assuming that not doing so implies the owner and
>> > > group that cfagent runs as). by storing that information,
>> > > you can cluster copy statements which all set the same
>> > > owner and group. i have no idea if this was intentional
>> > > or a feature.
>> > > i do like the idea of templates, though; has this been
>> > > discussed on the list before? i've found the ability to
>> > > use nesting templates in nagios very useful in keeping a
>> > > clean set of configuration files where identical information
>> > > is expressed numerous times. i dont know that i'd find it
>> > > as useful in cfengine config files but it's worth discussing.
>> > >
>> > > > There was the thought of having a template for copy statements
>> > > >
>> > > > template:
>> > > >
>> > > > root_executable
>> > > > owner=root
>> > > > group=root
>> > > > mode=0755
>> > > > server=$(server)
>> > > >
>> > > > copy:
>> > > >
>> > > > /var/tmp/somefile/
>> > > > dest=/var/tmp/somefile
>> > > > template=root_executable
>> > > >
>> > > > This seems like a good idea.
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > Help-cfengine mailing list
>> > > Help-cfengine@gnu.org
>> > > http://lists.gnu.org/mailman/listinfo/help-cfengine
>> >
>> >
>> >
>> > _______________________________________________
>> > Help-cfengine mailing list
>> > Help-cfengine@gnu.org
>> > http://lists.gnu.org/mailman/listinfo/help-cfengine
>
>
>
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272 Email: Mark.Burgess@iu.hio.no
Fax : +47 22453205 WWW : http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~