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

[Ed Brown]

I assume you are talking about 'remote methods'?  There's not much info
in the documentation about it yet, but it sure sounds complex, if not to
say convoluted.  For one, I'm guessing it requires that cfservd be
running everywhere.  If you are already doing that, then that wouldn't
be a big deal.  If you aren't, that's a considerable change, adding an
additional open port everywhere.

When I've considered data gathering schemes, I always end up back at the
idea of scp-ing info back to the server, or somewhere, an idea with its
own limitations and problems.  I'd be interested in hearing if you are
able to use cfengine for this.

-Ed


On Thu, 2004-10-21 at 16:02, Tod Oace wrote:
> > (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 <ebrown@lanl.gov>
> > Date: October 21, 2004 14:56:55 PDT
> > To: Tod Oace <tod.r.oace@intel.com>
> > 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
> > Help-cfengine@gnu.org
> > http://lists.gnu.org/mailman/listinfo/help-cfengine
> >