[Peep-develop] Re: Peep-develop digest, Vol 1 #2 - 2 msgs

[Michael G. <mg...@ee...>]

> Message: 2
> To: pee...@li...
> Date: Mon, 11 Dec 2000 17:57:00 -0600
> From: Nolan Darilek <no...@bi...>
> Subject: [Peep-develop] No sound
> 
> I've tried running the various utilities, based on my brief scan of
> the paper on the website.

  I sent a message about this earlier but it doesn't seem to
have gone through so I'll try again. I didn't have m mailer at the
time and that web interface didn't seem to work. Ugh.

> 
> I first tried running LogParser to determine which events were
> supported in /etc/peep.conf; here's a snippet of what I get:
> 
>     -events=[STRING]     The string of events to scan for. See below
>                          for a map of events to letter options.
>     -config=[PATH]       Path to the configuration file to use.
>     -logfile=[PATH]      The path of the logfile to scan.
>     -debug               Enable debugging
> 
> Generated options (by peep.conf):
> Exit 1
> 
> Where are the letter codes for the events?

  You set them yourself in peep.conf. To enable all the example
ones that I provide for in my paper, you'd do a:

  -events=IOLlUB

  Those options letters can be whatever you want and when you do
a -help, it should be telling you what those option letters are
if it can find your peep.conf. You should be able to do a:

  ./LogParser -config=/etc/peep.conf -help

  and have it tell you the generated options. If this doesn't work,
please let me know.

> 
> So I then loaded up /etc/peep.conf and found them. Then I reran
> LogParser the correct way and, though it reports matches for the
> events, I hear no sounds. Peepd appears to be running, however. My
> mixer is also properly set up. What should I try to resolve this? I've
> tried running Peck and KeyTest, but they don't seem to make sounds
> either (though that may just be user ignorance on my part.)

  Hmm, I'd test first with Peck since it's the easiest way
to establish that things work. Just do a Peck -server=<host>
-port=2001. KeyTest currently needs to be run on the machine local to
the server. If you're not hearing anything from logparser, then it
sounds like your auto-discovery stuff might not be set up right. But
before you can conclude that, make some noise with Peck first.

  I suggest compiling with ./configure --enable-debug=0 to help
diagnose your problem.

> 
> I'm also curious about how to use LogCheck correctly for multiple
> logfiles. Debian splits events into multiple logs; my
> incoming/outgoing mail is reported in /var/log/exim/mainlog, PAM sends
> login/logout notifications to auth.log, etc. Should I run one
> logparser instance for each file? Or is it possible to specify
> multiple logfile options?

  For multiple files, just separate your files by commas:

  -logfile="/var/log/messages,/var/log/auth.log"

  You should really only need one LogParser per machine.

  By the way, heads up on the new LogParser coming out in the next
release - 0.3.6 will make it so that if you can't get autodiscovery to
work or don't want to, you can use a:

  LogParser -server=<host> -port=<port> -noautodiscovery

> 
> Thanks!
> 
> 
> --__--__--
> 
> _______________________________________________
> Peep-develop mailing list
> Pee...@li...
> http://lists.sourceforge.net/mailman/listinfo/peep-develop
> 
> 
> End of Peep-develop Digest_______________________________________________
> Peep-develop mailing list
> Pee...@li...
> http://lists.sourceforge.net/mailman/listinfo/peep-develop
`-> (peep-develop-request)

-- 
Michael Gilfix
mg...@ee...