[Fwd: Re: ${clientip} ?]

[Ed Brown]

(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...)
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: ${clientip} ?
>
>
>
>
> Date: 
>
> Thu, 21 Oct 2004 15:56:55 -0600
>
>
>
>
> 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?  
>
> -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?
>
> --- End Message ---