help-cfengine
[Top][All Lists]
Advanced

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

Re: Getting $(allclasses) into a shellcommand


From: Chip Seraphine
Subject: Re: Getting $(allclasses) into a shellcommand
Date: Mon, 19 Jul 2004 14:58:47 -0500
User-agent: KMail/1.5.4

Yeah?  That would be wonderfully useful.  As it is, the last thing my cfengine 
runs do is something like this:

shellcommands:
        "/bin/echo $(allclasses) | cut -d= -f2- | tr ':' '\n' > 
$(workdir)/classlist"

Very useful for debugging.  Having an 'official' file would be quite handy, 
although it would have to be written to synchronously (so that shellcommands, 
modules, etc can use it to read the current state).



On Monday 19 July 2004 14:42, Mark.Burgess@iu.hio.no wrote:
> 
> Cfengine could easily cache the classes in an easily readble file format
> M
> 
> On 19 Jul, Chip Seraphine wrote:
> > The problem is doing the writing.  Unless I do something expensive 
involving 
> > an iterator, I can't get the class list into the file at all (even with 
> > editfiles).
> > 
> > On Monday 19 July 2004 14:09, Ted Zlatanov wrote:
> >> How about writing the list of classes into $cfinputs/classes.$$ where
> >> $$ is the PID of the cfagent run?  This can be passed as a variable
> >> to spawned processes thereafter (CFCLASSFILE, for example).  It's a
> >> temporary file but harmless if it's left around.
> >> 
> >> I can think of other solutions involving IPC but those are uglier by
> >> far.
> >> 
> >> Ted
> >> 
> > 
> 
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
> Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 

-- 

Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com





reply via email to

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