<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=937282018-19012006><FONT face=Arial color=#0000ff size=2>I was
thinking the same thing about using the config parameter of the
hobbit/bigbrother protocol. Only difference in what I was thinking was one large
global file i.e. in the format of the bb-msgstab. Running only every hour is too
long for me. Would need some type of tool to check the log(s) with only updated
info from the last time the log(s) were checked.</FONT></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Bob Gordon
[mailto:rgordonjr@gmail.com] <BR><B>Sent:</B> Thursday, January 19, 2006 12:58
PM<BR><B>To:</B> hobbit@hswn.dk<BR><B>Subject:</B> [hobbit] Client log parsing
(suggestion)<BR><BR></FONT></DIV>Hi Henrick -<BR><BR>In one of the previous
messages, you had mentioned that you wanted to keep as much configuration data
on the server as possible in order to make adminstration easier. To that end I
offer the following suggestion for the message configuration..<BR><BR>In the
bb man page (4.1.2 early snapshot) there is a section that reads as
follows:<BR><BR>>>>>>>>>>>>>>><BR>
config FILENAME<BR>
Retrieve one of the Hobbit configuration files from
the<BR> server. This
command allows a client to pull files
from<BR> the
$BBHOME/etc/ directory on the server, allowing
for<BR>
semi-automatic updates of the client
configuration.<BR> Since
the configuration files are designed to have
a<BR> common
file for the configuration of all hosts in
the<BR> system - and
this is in fact the recommended way
of<BR> configuring your
clients - this makes it easier to
keep<BR> the
configuration files
synchronized.<BR>>>>>>>>>>>>>>><BR><BR>Why
not set things up as follows:<BR>1 - On the server have a "hobbit-msg" file
that contains default configuration information that applies to all
systems. (I.E. Alert on kernel warning and panic messages from the
syslog).<BR>2 - In the same directory (or a subdirectory) have seperate
hobbit-msg.<servername> files that contain specific configuration
information for the specified hosts.<BR>3 - Once an hour (or other
configurable time frame) have the client systems issue a command to pull the
default file as well as the system specific file from the server. If the
client specific file is not available use the default file, otherwise use the
standard configuration..<BR><BR>Doing it this way would still allow for
central administration of the configuration files as well as allow for custom
message parsing configurations on the target systems..<BR><BR>Anyways..
Just a thought..<BR><BR>Later -<BR clear=all><BR>-- <BR>--==[ Bob Gordon ]==--
</BLOCKQUOTE></BODY></HTML>