[Top][All Lists]

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

Re: (perl)script for cfengine analysis

From: Nate Campi
Subject: Re: (perl)script for cfengine analysis
Date: Tue, 24 Dec 2002 11:51:37 -0800
User-agent: Mutt/1.3.28i

On Tue, Dec 24, 2002 at 12:07:58PM +0000, Thomas Glanzmann wrote:
> > I simply turned "Syslog = (on)" and used my existing syslog parsing
> > tools to read the cfengine output on a central loghost. Once my cfengine
> > configuration(s) started to stabilize I didn't generate too much
> > cfengine log traffic.
> > Of course I risk losing logs this way, since syslog over UDP (or even
> > TCP if connectivity is delayed for more than a moment) is unreliable.
> > The compromise is worth it in my case, since I didn't need new tools, I
> > could extend my current ones as needed.
> But my main problem is that cfengine spawns a script named update to update,
> install, deinstall packages. And I want the output sorted: Like
> cfengine did not run on the follwing hosts during the day: faui0bla, ...
> On 67 hosts happened the following during the day:
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following packages have been kept back
>   bsdutils mount util-linux 
> 0 packages upgraded, 0 newly installed, 0 to remove and 3  not upgraded.

This isn't tested, but you might be able to force the output into your
syslogs with something like this (should work, I pipe some stuff into
mailx in the same way):


        "/usr/local/sbin/ 2>&1 | logger -p local0.notice"
        timeout=600 # timeout=seconds

This way you can (again) leverage existing syslog parsing tools.

If this doesn't work (though I fully expect it to) you'd have to collect
the data somehow in a central spot via database insert, shared NFS
mount, CGI post, etc and parse it from there. That kinda sucks - maybe
somebody else has a better idea.
Nate Campi 

Our continuing mission: To seek out knowledge of C, to explore strange
UNIX commands, and to boldly code where no one has man page 4. 

reply via email to

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