help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fwd: Re: ${clientip} ?]


From: Tod Oace
Subject: Re: [Fwd: Re: ${clientip} ?]
Date: Thu, 21 Oct 2004 15:02:27 -0700

(Dang, I don't understand lists that don't set the reply-to field to go
to the list.  To me, that's the whole point of a list, the discussion,
not to get private answers to questions, unless appropriate for some
reason...)

Oh, and that case here's my reply to the list:

From: Ed Brown <address@hidden>
Date: October 21, 2004 14:56:55 PDT
To: Tod Oace <address@hidden>
Subject: Re: ${clientip} ?


Where I get stuck right away when considering something like this is the
question of how to get information from the client to the server.  It's
backwards to the normal flow of cfengine.  Did you already have a
mechanism for this in mind?

Yeah... A Cfengine method call. There's even an example in the reference manual passing the first part of /etc/passwd:

http://www.cfengine.org/docs/cfengine-Reference.html#methods

search for: ReadFile("/etc/passwd"

So I *think* that takes care of the communication mechanism. I'm toying with it now. But I'm also thinking about the step after that. -Tod


-Ed


On Thu, 2004-10-21 at 15:41, Tod Oace wrote:
I'm hoping to create a method to collect small bits of information from systems onto my cfengine servers. It seems like this will work fine but
I'd also like to prevent systems from being able to clobber each
others' bits of information.

I think what I want is to stash information into files named
.../somedirectory/${clientip}/${infotype} where ${infotype} comes from
the client and ${clientip} is defined on the server end. But I'm unable
to find a variable like ${clientip}. I see forcereplyto but that's
defined by the client.

I would like this in order to collect and analyze files before I put
them under central cfengine control. I don't really need information
sandboxes for that kind of temporary information, but there is some
other system information I would like to protectection for. Stuff
defined on the systems that I want persistent across system builds. Any
ideas?


_______________________________________________
Help-cfengine mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/help-cfengine

--
Tod Oace, Intel Corporation <address@hidden>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]