|
From: Collin S. <col...@co...> - 2003-09-27 22:57:17
|
tir, 2003-09-23 kl. 18:08 skrev John McCain: > Many thanks. > > > Can you send me the client output and the peep.conf your client is > > using? Try starting it with --debug=6 (lotta output) or --debug=9 (whoa > > nelly). Scuse the delay in reply. I got to see the best sysadmin I know get married yesterday :-) It looks like the peep.logtab file you sent along is in the old format. The new format has a "Group" column rather than the "Reference-Letter" column. This concept of a group is similar to the old reference-letter. You can decide to only use certain groups with the --groups option or exclude certain groups with the --exclude option. If you specify neither --groups or --exclude, all groups are considered active. The new format also has a "Host" column which allows the client (e.g., logparser) to only use that line of the configuration file if it is running on the provided host. The default of "localhost" or "127.0.0.1" means that the line is good on all hosts. Since you're not using autodiscovery, packets are sent back and forth only when events are triggered. Since the logparser had trouble parsing the events section of its config file (and hence didn't know about any events), you didn't see any network traffic. An example of a good peep.logtab file is attached. Set up some events for your system (I like to use the "bad-login" for testing) and trigger them. You should see some traffic on lo port 2001. Please let me know if you have additional questions or if you have any other problems. Cheers, -Collin -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Collin Starkweather, Ph.D col...@co... University of Colorado Department of Economics ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |