peep-develop — Mailing list for the usage and development of Peep

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

[Ian Hall-B. <ma...@ne...>]

On 13 Dec 2000, Nolan Darilek wrote:

> Where do I get Tail.pm? CPAN, or is it a part of Peep?

File::Tail

Marvelously useful module.

-Ian

--

"The French language, which the French used to learn very well, did not
exist for the sake of conveying information, for communicating men's
common needs; it was indistinguishable from historical consciousness.
Frenchness is defined by participation in this language, its literature
and the entire range of effects it produces."

				-- Allan Bloom
				   The Closing of The American Mind

Re: [Peep-develop] Cannot get different sounds

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

  Heh, my fault on this one. I goofed. Download 0.3.6 again. Heh. I
forgot to add 5 lines of code =) You're my first tester to use the
-noautodiscovery option. That problem should be all fixed.

On Wed, Dec 13 @ 14:00, Edvard Majakari wrote:
> On Wed, 13 Dec 2000, mg...@ee... wrote:
> 
> I promise (yeah, sure) this is last stupid question concerning peep.. I
> use version 0.3.6, and I just got it work fine from the remote host. But
> only one thing - I cannot get the rooster sound for web pages. Also,
> ssh-login, su and web seem to generate the same sounds, even as they
> should use different sound files. 
> 
> Setup: I have peepd running (with no options) at machine A, 
> with the following /etc/peep.conf (comments removed to save space)
> 
> --------/etc/peep.conf at machine A, where peepd is running------------------------
> 
> class text
>   broadcast broad.cast.address.0
>   server my.FQDN:2001
> end class text
> 
> client LogParser
>   class text test
>   port 2000
>   config
>     # use postfix pattern because I don't use sendmail
>     out-mail           O             0           1            "postfix.*:.*from="
>     inc-mail           I            255          0            "postfix.*:.*to="
>     login              L            128          0            "Login"
>     logout             l            128          0            "Logout"
>     ssh-logins        S            128          2            "(ssh).*opened"
>     bad-query         Q            128          3            "unapproved query"
>     web               W            128          0            "GET"  
>     su                U            128         255           "(su.*root)|(su: SU)"
>     badsu             B            128         255           "BADSU"
>   end config
> end client LogParser
> 
> events
>   inc-mail /usr/local/share/peep/sounds/cleanpeep.* 1        
>   login /usr/local/share/peep/sounds/jay2.* 1               
>   out-mail /usr/local/share/peep/sounds/peep1a.*  2         
>   logout /usr/local/share/peep/sounds/croak.* 3             
>   ssh-logins /usr/local/share/peep/sounds/tink2a.* 1 # sound of ssh
>   web /home/ed/Peep-0.3.6/sounds/myrooster1.* 1  # web sound
>   su /usr/local/share/peep/sounds/unk12.* 1      # su sound
>   bad-query /usr/local/share/peep/sounds/unk15a.* 1
>   badsu /usr/local/share/peep/sounds/unk7.* 1  
> end events
> 
> states
>   loadavg /usr/local/share/peep/sounds/water2.*       8  0.7 # Stream...  standard
>   users   /usr/local/share/peep/sounds/s-01-31-01-s.* 1  1.5
>   something /usr/local/share/peep/sounds/leaves.*     4  0.7 
>   cricket   /usr/local/share/peep/sounds/s-01-47-01-s.* 1 0.0 # needs fixing
> end states
> 
> -----------------------------------------------------------------------------------
> 
> Then, in the machine B I have both the Uptime and LogParser running as
> follows:
> 
> ./Uptime -server=machine.a.address -port=2001
> 
> This works well; I hear water running with intensity correlating to load
> average.
> 
> 
> But the LogParser - I don't know, it seems to work ok, it matches the
> patterns and I hear noises.. except they are all the same. I run LogParser
> as follows:
> 
> <machine B> $ sudo ./LogParser -noautodiscovery -server <machine A>
>               -port 2001 -events="IOLlSQUBW" 
>               -logfile="/var/log/auth.log,/var/log/syslog,/var/log/daemon.log,/var/log/mail.info,/var/log/apache/access.log"
> 
> And I get
> 
> =============================================================
> LogParser - Event producer for PEEP: the network auralizer
> Copyright (c) 2000 Michael Gilfix
> =============================================================
> Initializing PEEP library and retrieving config...(done)
> Patterns Loaded: 9
> Scanning logs:
>         /var/log/auth.log
>         /var/log/syslog
>         /var/log/daemon.log
>         /var/log/mail.info
>         /var/log/apache/access.log
> Found match: su: Dec 13 13:36:11...
> Found match: web: ... "GET / HTTP/1.0" ..
> Found match: ssh-logins: Dec 13 13:43:40 ...
> 
> and I always get the same, short whistle. In machine B (where I run
> LogParser) I have this peep.conf:
> 
> 
> -------------- /etc/peep.conf at Machine B, where I run LogParser --------
> class text
>   broadcast broadcast.address
>   server machine.A.FQDN:2001
> end class text
> 
> client LogParser
>   class text test
>   port 2000
>   config
>     out-mail           O             0           1            "postfix.*:.*from"
>     inc-mail           I            255          0            "postfix.*:.*to="
>     login              L            128          0            "Login"
>     logout             l            128          0            "Logout"
>     ssh-logins        S            128          2            "(ssh).*opened"
>     web               W            128          0            "GET"
>     bad-query         Q            128          3            "unapproved query"
>     su                U            128         255           "(su.*root)|(su: SU)"
>     badsu             B            128         255           "BADSU"
>   end config
> end client LogParser
> 
> events
> inc-mail /home/ed/Peep-0.3.6/sounds/cleanpeep.* 1       # fine..
> login /home/ed/Peep-0.3.6/sounds/jay2.* 1               # Great sound
> out-mail /home/ed/Peep-0.3.6/sounds/peep1a.*  2             # Fine
> logout /home/ed/Peep-0.3.6/sounds/croak.* 3                # 3 frog sounds.
> web /home/ed/Peep-0.3.6/sounds/myrooster1.* 1 
> ssh-logins /home/ed/Peep-0.3.6/sounds/tink2a.* 1
> su /home/ed/Peep-0.3.6/sounds/unk12.* 1                # The monkey bird. USE
> bad-query /home/ed/Peep-0.3.6/sounds/unk15a.* 1        # This is great -hoarse
> badsu /home/ed/Peep-0.3.6/sounds/unk7.* 1            # This is also great. USE
> end events
> 
> states
>  loadavg  /home/ed/Peep-0.3.6/sounds/water2.*  8     0.7 # Stream...  standard
>  users    /home/ed/Peep-0.3.6/sounds/s-01-31-01-s.* 1 1.5
>  something /home/ed/Peep-0.3.6/sounds/leaves.* 4  0.7 
>  cricket   /home/ed/Peep-0.3.6/sounds/s-01-47-01-s.* 1 0.0 # needs fixing
> end states
> 
> --------------------------------------------------------------------------
> 
> Of course, all works fine if myrooster1.01, tink2a.01 and unk12.01 are all
> the same-sounding files. 
> 
> -- 
> # Edvard	050 3691 463	http://www.uta.fi/~loedma/
> 
> -- rakastan, siis olen
> _______________________________________________
> Peep-develop mailing list
> Pee...@li...
> http://lists.sourceforge.net/mailman/listinfo/peep-develop
`-> (ed)

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

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

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

On Wed, Dec 13 @ 02:18, Nolan Darilek wrote:
> >>>>> "Michael" == Michael Gilfix <mg...@ee...> writes:
> 
>     Michael>   I'm not sure what to suggest at this point... Have you
>     Michael> checked your mixer (perhaps peepd is playing on a channel
>     Michael> that's turned down?).
> 
> Aha! :)
> 
> I basically set every channel I had to maximum, and now Peck plays
> soothing water noises -- very stress-relieving for someone who's been
> really trying to get this beast working. :)

  Woo hoo! And I was thinking I had a major bug to contend with. Heh.

> 
> Now I have another problem, though this one's probably much more
> solvable. I just grabbed the new release:
> 
> ethereal:~/src/peep/Peep-0.3.6/utils> ./LogParser 
> Can't locate File/Tail.pm in @INC (@INC contains: /usr/lib/perl5 /usr/lib/perl5/5.6/i386-linux /usr/lib/perl5/5.6 /usr/local/lib/site_perl/i386-linux /usr/local/lib/site_perl /usr/lib/perl5/5.005/i386-linux /usr/lib/perl5/5.005 .) at ./LogParser line 25.
> BEGIN failed--compilation aborted at ./LogParser line 25.
> Exit 2
> 
> Where do I get Tail.pm? CPAN, or is it a part of Peep?

  Very solveable.. Just grab it off of CPAN.

> 
> Thanks!
`-> (nolan_d)

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

[Peep-develop] Cannot get different sounds

[Edvard M. <ed...@hy...>]

On Wed, 13 Dec 2000, mg...@ee... wrote:

I promise (yeah, sure) this is last stupid question concerning peep.. I
use version 0.3.6, and I just got it work fine from the remote host. But
only one thing - I cannot get the rooster sound for web pages. Also,
ssh-login, su and web seem to generate the same sounds, even as they
should use different sound files. 

Setup: I have peepd running (with no options) at machine A, 
with the following /etc/peep.conf (comments removed to save space)

--------/etc/peep.conf at machine A, where peepd is running------------------------

class text
  broadcast broad.cast.address.0
  server my.FQDN:2001
end class text

client LogParser
  class text test
  port 2000
  config
    # use postfix pattern because I don't use sendmail
    out-mail           O             0           1            "postfix.*:.*from="
    inc-mail           I            255          0            "postfix.*:.*to="
    login              L            128          0            "Login"
    logout             l            128          0            "Logout"
    ssh-logins        S            128          2            "(ssh).*opened"
    bad-query         Q            128          3            "unapproved query"
    web               W            128          0            "GET"  
    su                U            128         255           "(su.*root)|(su: SU)"
    badsu             B            128         255           "BADSU"
  end config
end client LogParser

events
  inc-mail /usr/local/share/peep/sounds/cleanpeep.* 1        
  login /usr/local/share/peep/sounds/jay2.* 1               
  out-mail /usr/local/share/peep/sounds/peep1a.*  2         
  logout /usr/local/share/peep/sounds/croak.* 3             
  ssh-logins /usr/local/share/peep/sounds/tink2a.* 1 # sound of ssh
  web /home/ed/Peep-0.3.6/sounds/myrooster1.* 1  # web sound
  su /usr/local/share/peep/sounds/unk12.* 1      # su sound
  bad-query /usr/local/share/peep/sounds/unk15a.* 1
  badsu /usr/local/share/peep/sounds/unk7.* 1  
end events

states
  loadavg /usr/local/share/peep/sounds/water2.*       8  0.7 # Stream...  standard
  users   /usr/local/share/peep/sounds/s-01-31-01-s.* 1  1.5
  something /usr/local/share/peep/sounds/leaves.*     4  0.7 
  cricket   /usr/local/share/peep/sounds/s-01-47-01-s.* 1 0.0 # needs fixing
end states

-----------------------------------------------------------------------------------

Then, in the machine B I have both the Uptime and LogParser running as
follows:

./Uptime -server=machine.a.address -port=2001

This works well; I hear water running with intensity correlating to load
average.


But the LogParser - I don't know, it seems to work ok, it matches the
patterns and I hear noises.. except they are all the same. I run LogParser
as follows:

<machine B> $ sudo ./LogParser -noautodiscovery -server <machine A>
              -port 2001 -events="IOLlSQUBW" 
              -logfile="/var/log/auth.log,/var/log/syslog,/var/log/daemon.log,/var/log/mail.info,/var/log/apache/access.log"

And I get

=============================================================
LogParser - Event producer for PEEP: the network auralizer
Copyright (c) 2000 Michael Gilfix
=============================================================
Initializing PEEP library and retrieving config...(done)
Patterns Loaded: 9
Scanning logs:
        /var/log/auth.log
        /var/log/syslog
        /var/log/daemon.log
        /var/log/mail.info
        /var/log/apache/access.log
Found match: su: Dec 13 13:36:11...
Found match: web: ... "GET / HTTP/1.0" ..
Found match: ssh-logins: Dec 13 13:43:40 ...

and I always get the same, short whistle. In machine B (where I run
LogParser) I have this peep.conf:


-------------- /etc/peep.conf at Machine B, where I run LogParser --------
class text
  broadcast broadcast.address
  server machine.A.FQDN:2001
end class text

client LogParser
  class text test
  port 2000
  config
    out-mail           O             0           1            "postfix.*:.*from"
    inc-mail           I            255          0            "postfix.*:.*to="
    login              L            128          0            "Login"
    logout             l            128          0            "Logout"
    ssh-logins        S            128          2            "(ssh).*opened"
    web               W            128          0            "GET"
    bad-query         Q            128          3            "unapproved query"
    su                U            128         255           "(su.*root)|(su: SU)"
    badsu             B            128         255           "BADSU"
  end config
end client LogParser

events
inc-mail /home/ed/Peep-0.3.6/sounds/cleanpeep.* 1       # fine..
login /home/ed/Peep-0.3.6/sounds/jay2.* 1               # Great sound
out-mail /home/ed/Peep-0.3.6/sounds/peep1a.*  2             # Fine
logout /home/ed/Peep-0.3.6/sounds/croak.* 3                # 3 frog sounds.
web /home/ed/Peep-0.3.6/sounds/myrooster1.* 1 
ssh-logins /home/ed/Peep-0.3.6/sounds/tink2a.* 1
su /home/ed/Peep-0.3.6/sounds/unk12.* 1                # The monkey bird. USE
bad-query /home/ed/Peep-0.3.6/sounds/unk15a.* 1        # This is great -hoarse
badsu /home/ed/Peep-0.3.6/sounds/unk7.* 1            # This is also great. USE
end events

states
 loadavg  /home/ed/Peep-0.3.6/sounds/water2.*  8     0.7 # Stream...  standard
 users    /home/ed/Peep-0.3.6/sounds/s-01-31-01-s.* 1 1.5
 something /home/ed/Peep-0.3.6/sounds/leaves.* 4  0.7 
 cricket   /home/ed/Peep-0.3.6/sounds/s-01-47-01-s.* 1 0.0 # needs fixing
end states

--------------------------------------------------------------------------

Of course, all works fine if myrooster1.01, tink2a.01 and unk12.01 are all
the same-sounding files. 

-- 
# Edvard	050 3691 463	http://www.uta.fi/~loedma/

-- rakastan, siis olen

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

[Edvard M. <ed...@hy...>]

On 13 Dec 2000, no...@bi... wrote:

> Where do I get Tail.pm? CPAN, or is it a part of Peep?

(as root)
# perl -MCPAN -e shell

install File::Tail

(also, commanding just 'cpan' on the command prompt might work).

-- 
# Edvard	050 3691 463	http://www.uta.fi/~loedma/

-- rakastan, siis olen

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

[Nolan D. <no...@bi...>]

>>>>> "Michael" == Michael Gilfix <mg...@ee...> writes:

    Michael>   I'm not sure what to suggest at this point... Have you
    Michael> checked your mixer (perhaps peepd is playing on a channel
    Michael> that's turned down?).

Aha! :)

I basically set every channel I had to maximum, and now Peck plays
soothing water noises -- very stress-relieving for someone who's been
really trying to get this beast working. :)

Now I have another problem, though this one's probably much more
solvable. I just grabbed the new release:

ethereal:~/src/peep/Peep-0.3.6/utils> ./LogParser 
Can't locate File/Tail.pm in @INC (@INC contains: /usr/lib/perl5 /usr/lib/perl5/5.6/i386-linux /usr/lib/perl5/5.6 /usr/local/lib/site_perl/i386-linux /usr/local/lib/site_perl /usr/lib/perl5/5.005/i386-linux /usr/lib/perl5/5.005 .) at ./LogParser line 25.
BEGIN failed--compilation aborted at ./LogParser line 25.
Exit 2

Where do I get Tail.pm? CPAN, or is it a part of Peep?

Thanks!

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

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

On Wed, Dec 13 @ 00:45, Nolan Darilek wrote:
> >>>>> "Michael" == Michael Gilfix <mg...@ee...> writes:
> 
>     Michael>   In other words, it looks great. So, now I'd start
>     Michael> looking at your sound stuff. What system you on? If on
>     Michael> redhat, check aumix or something of that sort. Make sure
>     Michael> you can play mp3s.. Hopefully, you've compiled with
>     Michael> /dev/audio support (DEVICE_DRIVER) - try using /dev/dsp
>     Michael> instead.  But your peck is working .. it's just having
>     Michael> problems playing sounds.  At least now you know where the
>     Michael> problem is.
> 
> Hmm. I use freeamp/mpg123/xawtv/quake here regularly, and sound works
> beautifully. I'm on Debian 2.2 with a bit o' unstable thrown in for
> good measure, 2.4.0test10, with ALSA 0.59d (Which, IIRC, emulates OSS
> quite well.) I'm using an SBLive! Value.

  Yeah, I know the OSS emulation works great.. I had done my original
development of /dev/audio stuff with its emulation..

> 
> For kicks I shut down ALSA and loaded the vanilla emu10k1 driver, but
> this didn't resolve the issue either.

  I use the emu10k1 driver that comes with linux kernel 2.2.17... Not
sure that will help any.

> 
> I'm a bit confused by your suggestion that I use /dev/dsp instead of
> /dev/audio. How do I do this? I thought that each device served a
> different function.

  I've found with my SB LIVE that /dev/dsp would play files instead of
/dev/audio when I had had a botched setup. I'm not exactly sure what
the difference is between the two but I think that /dev/audio is just
the generic sound interface while /dev/dsp is for digital sound.

  I'm not sure what to suggest at this point... Have you checked
your mixer (perhaps peepd is playing on a channel that's turned
down?).

  Does anyone else have Peep working on Debian that can make some
suggestions?

> 
`-> (nolan_d)

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

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

[Nolan D. <no...@bi...>]

>>>>> "Michael" == Michael Gilfix <mg...@ee...> writes:

    Michael>   In other words, it looks great. So, now I'd start
    Michael> looking at your sound stuff. What system you on? If on
    Michael> redhat, check aumix or something of that sort. Make sure
    Michael> you can play mp3s.. Hopefully, you've compiled with
    Michael> /dev/audio support (DEVICE_DRIVER) - try using /dev/dsp
    Michael> instead.  But your peck is working .. it's just having
    Michael> problems playing sounds.  At least now you know where the
    Michael> problem is.

Hmm. I use freeamp/mpg123/xawtv/quake here regularly, and sound works
beautifully. I'm on Debian 2.2 with a bit o' unstable thrown in for
good measure, 2.4.0test10, with ALSA 0.59d (Which, IIRC, emulates OSS
quite well.) I'm using an SBLive! Value.

For kicks I shut down ALSA and loaded the vanilla emu10k1 driver, but
this didn't resolve the issue either.

I'm a bit confused by your suggestion that I use /dev/dsp instead of
/dev/audio. How do I do this? I thought that each device served a
different function.

[Peep-develop] New release available - Peep 0.3.6

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

  A new Peep version is available which fixes bugs with LogParser
as well as provides a temporary solution to fixing the segfaulting
problem on server startup. The release is currently only available
from the homepage temporarily while sourceforge file releasing service
remains down. I suggest everyone grab the release though...

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

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

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

On Tue, Dec 12 @ 20:00, Nolan Darilek wrote:
> Peck doesn't work for me at all, either. It doesn't do anything. I've
> tried running it on everything from 2000-2003, but no luck. I also
> scrapped my peep.conf and started over, but that didn't work either.
> 
>     Michael>   I suggest compiling with ./configure --enable-debug=0
>     Michael> to help diagnose your problem.
> 
> Done. When I run ./Peck without the -server/-port options, I receive:
> Server received a packet: Received size: 10 and struct Packet size: 136
> Packet header:
> Major ver: 1
> Minor ver: 0
> Type: 4
> Reserved: 0
> Got client event
> 
> Received Event:
> Event.type -> 1
> Event.sound -> 0
> Event->location -> 128
> Event->volume -> 0.501961
> Event->priority -> 0
> Event->dither -> 255
> Event->mix_in_time -> 0
> 
> Fade value was 255. Ignoring...
> Set StateVolumes[0] to 0.050196
> Set StateFade[0] to 0.700000
> <and a bit later>
> Received alarm. Letting valid clients know we're still alive...
> Have 0 host entries prior to purge...
> Purged 0 hosts...
> 
> This also looks the same when I use -server/port.
> 
> Hmmm...the plot thickens. :)
>
   Heh. That sort of output means it received the packet correctly.
By default, Peck sends a singla for a state sound (type == 1) with
(sound == 0)... 

  The alarm is just the mechanism which tells Peep to wake up and
check it's hostlist to see if it no longer needs to keep track
of clients. 

  In other words, it looks great. So, now I'd start looking at your
sound stuff. What system you on? If on redhat, check aumix or something
of that sort. Make sure you can play mp3s.. Hopefully, you've compiled
with /dev/audio support (DEVICE_DRIVER) - try using /dev/dsp instead.
But your peck is working .. it's just having problems playing sounds.
At least now you know where the problem is. 

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

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

[Nolan D. <no...@bi...>]

>>>>> "Michael" == Michael Gilfix <mg...@ee...> writes:

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

I received something earlier, actually.

    Michael>   ./LogParser -config=/etc/peep.conf -helpethereal:~/src/peep/Peep-0.3.4/utils> ls -l /etc/peep.conf
lrwxrwxrwx    1 root     root           24 Dec 10 17:09 /etc/peep.conf -> /usr/local/etc/peep.conf
ethereal:~/src/peep/Peep-0.3.4/utils> ls -l /usr/local/etc/peep.conf
lrwxrwxrwx    1 root     root           26 Dec 10 17:08 /usr/local/etc/peep.conf -> ../stow/peep/etc/peep.conf
ethereal:~/src/peep/Peep-0.3.4/utils> ls /usr/local/stow/peep/etc/peep.conf -l
-rw-r--r--    1 root     staff        6510 Dec 11 17:42 /usr/local/stow/peep/etc/peep.conf
ethereal:~/src/peep/Peep-0.3.4/utils> ./LogParser -config=/etc/peep.conf -help
Unknown option: help
=============================================================
LogParser - Event producer for PEEP: the network auralizer
Copyright (c) 2000 Michael Gilfix
=============================================================

LogParser command line options:
  Valid options are:
    -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

My peep.conf is there; it's just buried behind a few symlinks due to
stow.

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

Peck doesn't work for me at all, either. It doesn't do anything. I've
tried running it on everything from 2000-2003, but no luck. I also
scrapped my peep.conf and started over, but that didn't work either.

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

Done. When I run ./Peck without the -server/-port options, I receive:
Server received a packet: Received size: 10 and struct Packet size: 136
Packet header:
Major ver: 1
Minor ver: 0
Type: 4
Reserved: 0
Got client event

Received Event:
Event.type -> 1
Event.sound -> 0
Event->location -> 128
Event->volume -> 0.501961
Event->priority -> 0
Event->dither -> 255
Event->mix_in_time -> 0

Fade value was 255. Ignoring...
Set StateVolumes[0] to 0.050196
Set StateFade[0] to 0.700000
<and a bit later>
Received alarm. Letting valid clients know we're still alive...
Have 0 host entries prior to purge...
Purged 0 hosts...

This also looks the same when I use -server/port.

Hmmm...the plot thickens. :)

[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...

[Peep-develop] No sound

[Nolan D. <no...@bi...>]

I've tried running the various utilities, based on my brief scan of
the paper on the website.

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?

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.)

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?

Thanks!

[Peep-develop] Re: Segfault fixed, now what? :)

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

> I fixed my broadcast address, and now the server seems to find my IP
> and bind to it, but now I'm having more problems. :)
> 
> I'm a bit confused about what's supposed to happen when I launch
> peepd. Will it create a fairly constant mix of ambient sound, or does
> it only make sounds occasionally? It's been running for several
> minutes and, though I can play MP3's and such nicely, I don't receive
> any sound. I'll include my config file below; I was a bit confused and
> may have mucked with something that I shouldn't have. I had to change
> some ports as to not conflict with some of the stuff that I'm running
> locally.

  The peep server just waits to receive sound data and then plays
them.  You need to run the utilities (Namely LogParser and Uptime) to
produce sound. You might also want to experiment with KeyTest, which
maps all the events and states to keys (you can change the volume and
stereo and stuff with the numbers keys and a shift combination).


> I'm a bit confused about:
> #a /usr/local/lib/peep/sounds/unk9.* 1                 # bah..
> and lines like that. Are those sounds which I can use for other
> events?

  Yeah.. the comments next to them detail the sound work I need to do
to fix some of them up. But they're guidlines on what Alva couch and I
felt were the quality of the sounds. Use the valid entries as examples.
So that:
a /usr/local/lib/peep/sounds/unk9.*    1 #comment

is 

mail /usr/local/lib/peep/sounds/unk9.* 1 #This is a mail event

  I suggest looking at the paper for now (Available off the website)
in order to figure out how this works..

> 
> And, out of curiosity, where does peepd get its logging information? I
> don't recall being able to specify a logfile to read from. What does
> the client LogParser section handle?

  LogParser reads logging information and produces sound event stuff .
The server just plays arbitrary sound data                           .

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

[Peep-develop] Segfault fixed, now what? :)

[Nolan D. <no...@bi...>]

I fixed my broadcast address, and now the server seems to find my IP
and bind to it, but now I'm having more problems. :)

I'm a bit confused about what's supposed to happen when I launch
peepd. Will it create a fairly constant mix of ambient sound, or does
it only make sounds occasionally? It's been running for several
minutes and, though I can play MP3's and such nicely, I don't receive
any sound. I'll include my config file below; I was a bit confused and
may have mucked with something that I shouldn't have. I had to change
some ports as to not conflict with some of the stuff that I'm running
locally.

--------------------------------------------------------------------------------
#Peep (the network auralizer) - Main configuration file

class text
  broadcast 129.116.21.255:2001
  server ethereal:2002
end class text

client LogParser
  class text test
  port 2003
  config
    # All patterns matched are done using Perl/awk matching syntax
    # Note: This configuration file generates the arguements to the
    #       log parser as well as its usage message (So you don't
    #       have to keep referring back here)
    #
    # Reserved Option letters are: -r (For remote host) -p (For port)
    #                              -c (Path to config file)
    # Commented lines are ones that BEGIN with a '#'
    #·
    # Name       Option-Letter    Location     Priority             Pattern·
    #
    out-mail           O             0           1            "sendmail.*:.*from=<.*@(\w+\.)?eecs.tufts.edu>"
    inc-mail           I            255          0            "sendmail.*:.*to=(\"|<.*@(\w+\.)?eecs.tufts.edu>).*stat=Sent"
    login              L            128          0            "Login"
    logout             l            128          0            "Logout"
#    ssh-logins        S            128          2            "sshd.*Connection from"
    bad-query         Q            128          3            "unapproved query"
    su                U            128         255           "(su.*root)|(su: SU)"
    badsu             B            128         255           "BADSU"
#    lowspace          L            128          4            "NOQUEUE: low on space"
#    rsh-stuff         R            128          5            "in\.r(exec|sh|login)d"
#    telnetd           T            128          6            "in\.telnetd"
  end config
end client LogParser

events
#Event Type      |          Path to Sound File           | # of sounds to load
#a /usr/local/lib/peep/sounds/bells1a.* 1            # Need more volume - Bells
#a /usr/local/lib/peep/sounds/bells1b.* 1            # Need more volume - Bells
#a /usr/local/lib/peep/sounds/bells2a.* 1            # Need more volume - Bells
#a /usr/local/lib/peep/sounds/bells3a.* 1            # Need more volume - Bells
#a /usr/local/lib/peep/sounds/blackbird1a.* 1        # need to split into 2 - red wing blackbird
#a /usr/local/lib/peep/sounds/cardinal1.* 1          # need to split it and use for something frequent
inc-mail /usr/local/lib/peep/sounds/cleanpeep.* 1          # fine..
#a /usr/local/lib/peep/sounds/door1a.* 1             # Should be split, has silence in the middle
#a /usr/local/lib/peep/sounds/doorbell1a.* 1         # fine 
#a /usr/local/lib/peep/sounds/goose1a.* 1            # split into 2
login /usr/local/lib/peep/sounds/jay2.* 1               # Great sound
#a /usr/local/lib/peep/sounds/myrooster1.* 1         # Fine, a little long, but use infreq.
out-mail /usr/local/lib/peep/sounds/peep1a.*  2             # Fine
a /usr/local/lib/peep/sounds/peep2b.* 1             # Fine
#a /usr/local/lib/peep/sounds/redwing2.* 1           # GET RID OF THIS
#a /usr/local/lib/peep/sounds/robin1a.* 1            # That's great
#a /usr/local/lib/peep/sounds/s-01-02-01-e-04-01.* 1 # Split.   -red wing blackbird
#a /usr/local/lib/peep/sounds/s-01-03-01-e-04-04.* 1 # Fine but long
a /usr/local/lib/peep/sounds/s-01-04-01-e-04-09.* 1 # Fine but long - I like this one
#a /usr/local/lib/peep/sounds/s-01-05-01-e-02-05.* 1 # Good redwing blackbird (Primary song)
#a /usr/local/lib/peep/sounds/s-01-05-02-e-01-02.* 1 # Single redwing blackbird call (Call)
#a /usr/local/lib/peep/sounds/s-01-05-03-e-02-07.* 1 # Cute.
#a /usr/local/lib/peep/sounds/s-01-06-01-e-07-03.* 1 # Long.. use infreq. - Robin.
#a /usr/local/lib/peep/sounds/s-01-07-01-e-01-01.* 1  # This is fantastic. - Cardinal
#a /usr/local/lib/peep/sounds/s-01-10-01-e-02-01.* 1  # This is great.
#a /usr/local/lib/peep/sounds/s-01-10-01-e-05-06.* 1  # This is good.
#a /usr/local/lib/peep/sounds/s-01-13-01-e-01-10.* 1  # This is great.
#a /usr/local/lib/peep/sounds/s-01-13-02-e-02-10.* 1  # Better Cardinal.
a /usr/local/lib/peep/sounds/s-01-15-01-e-01-01.* 1  # Hoot - we should use this (mourning dove)
#a /usr/local/lib/peep/sounds/s-01-16-01-e-01-10.* 1  # Good chirp - short call
#a /usr/local/lib/peep/sounds/s-01-33-01-e-03-03.* 1  # bah.. it's alright.
#a /usr/local/lib/peep/sounds/s-01-33-02-e-01-01.* 1  # Good chirp - Jay
logout /usr/local/lib/peep/sounds/croak.* 3                # 3 frog sounds.
#a /usr/local/lib/peep/sounds/s-01-36-01-e-01-01.* 1  # A little light but good
#a /usr/local/lib/peep/sounds/s-01-39-01-e-03-05.* 1  # Great.. thrush
#a /usr/local/lib/peep/sounds/s-01-43-01-e-07-02.* 1  # GET RID OF THIS - Processing errors
#a /usr/local/lib/peep/sounds/s-01-50-01-e-08-02.* 1  # Long but good
#a /usr/local/lib/peep/sounds/s-01-51-e-10-01.* 1     # Clipping problem but mourning dove. Fix
#a /usr/local/lib/peep/sounds/s-01-62-01-e-01-01.* 1  # Great little chirp
#a /usr/local/lib/peep/sounds/samp1a.* 1              # Long but good
a /usr/local/lib/peep/sounds/sigh.* 1                # Great - use - Eastern Phoebe
a /usr/local/lib/peep/sounds/tap1a.* 1               # Tap on tin roof - great
a /usr/local/lib/peep/sounds/tink2a.* 1              # Good  - water on aluminum
#a /usr/local/lib/peep/sounds/tink2b.* 1              # Good - hollower
#a /usr/local/lib/peep/sounds/unk10a.* 1              # Good long sound
#a /usr/local/lib/peep/sounds/unk11.* 1                # Very long but good for an event
su /usr/local/lib/peep/sounds/unk12.* 1                # The monkey bird. USE
bad-query /usr/local/lib/peep/sounds/unk15a.* 1               # This is great - hoarse
#a /usr/local/lib/peep/sounds/unk17a.* 1               # Same bird as last but good
#a /usr/local/lib/peep/sounds/unk22b.* 1               # Cardinal.. long-er
#a /usr/local/lib/peep/sounds/unk3a.* 1                # Great. Monkey bird.
badsu /usr/local/lib/peep/sounds/unk7.* 1                 # This is also great. USE
#a /usr/local/lib/peep/sounds/unk9.* 1                 # bah..
end events

states
#Event Type    |       Path to Sound File                      | # of sounds to load |  Fade between time
loadavg               /usr/local/lib/peep/sounds/water2.*      8                  0.7 # Stream...  standard
users               /usr/local/lib/peep/sounds/s-01-31-01-s.* 1                 1.5
something             /usr/local/lib/peep/sounds/leaves.*      4                  0.7 # 
cricket                  /usr/local/lib/peep/sounds/s-01-47-01-s.* 1              0.0 # this is great but timing at end of sound needs to be fixed
end states
--------------------------------------------------------------------------------

I'm a bit confused about:
#a /usr/local/lib/peep/sounds/unk9.* 1                 # bah..
and lines like that. Are those sounds which I can use for other
events?

And, out of curiosity, where does peepd get its logging information? I
don't recall being able to specify a logfile to read from. What does
the client LogParser section handle?

Thanks.

Re: [Peep-develop] Building peep using ALSA?

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

>Apologies if this issue is being beaten to death as I write this, and
>if the list archives haven't caught up (nothing is listed for this
>month.)

  No worries, the mailing list has only been around for a week.

>
>I'm trying to build peep on my Debian 2.2/2.3 box, using ALSA
>0.59D. I'm encountering several issues, and have run into a stumbling
>block.
>
>First, let me just state that I'm not an ALSA expert. The extent of my
>efforts to fix these apparent ALSA difficulties involves changing a
>few type names, etc.

  You and me both =)

>
>First, I encountered this error:
>
>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.    -g -O2 -c VoiceMixer.c
>VoiceMixer.c: In function `MixerInit':
>VoiceMixer.c:49: `SND_PCM_OPEN_PLAYBACK' undeclared (first use in this function)
>VoiceMixer.c:49: (Each undeclared identifier is reported only once
>VoiceMixer.c:49: for each function it appears in.)
>VoiceMixer.c:55: `SND_PCM_SFMT_S16_LE' undeclared (first use in this function)
>make[2]: *** [VoiceMixer.o] Error 1
>make[2]: Leaving directory `/home/nolan/src/peep/Peep-0.3.4/server'
>
>I looked at Sound.h, and the following lines were commented out:
>
>/* Include these headers for ALSA definitions */
>#include <sys/asoundlib.h>
>#include <linux/asound.h>
>/*#include <linux/asoundid.h>*/
>
>I uncommented them, and commented out the last include which I don't
>seem to have in my version of ALSA. It seems odd that the includes
>were commented out while the defines were not; is ALSA support not
>up-to-date?

  Other ALSA people have written me and had the same problems.  My
general guidelines are: Are you sure that headers and libraries are
installed (not just alsa drivers and utils)... Also, it may be out of
date because when I had written the code, it was back in version 0.4.x
or so.. I'll probably have to download the new version and update
it. But ALSA has been moving fast lately.

  I suggest that if you have the libraries and headers, just edit
your config.h and undef ALSA and define DEVICE_DRIVER. That will use
/dev/audio and should get you going. If anyone can provide me with a
patch or fix for ALSA, I'd appreciate it..


>
>VoiceMixer.c compiles, and everything runs smoothly until AlsaSound.c:
>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.    -g -O2 -c AlsaSound.c
>AlsaSound.c: In function `GetSoundCardInfo':
>AlsaSound.c:47: `snd_pcm_playback_info_t' undeclared (first use in this function)
>AlsaSound.c:47: (Each undeclared identifier is reported only once
>AlsaSound.c:47: for each function it appears in.)
>AlsaSound.c:47: `info' undeclared (first use in this function)
>AlsaSound.c:48: parse error before `static'
>AlsaSound.c:51: `err' undeclared (first use in this function)
>AlsaSound.c:53: warning: passing arg 2 of `strcat' makes pointer from integer
>without a cast
>AlsaSound.c:59: `s' undeclared (first use in this function)
>AlsaSound.c: In function `GetSoundStatus':
>AlsaSound.c:70: `snd_pcm_playback_status_t' undeclared (first use in this function)
>AlsaSound.c:70: `status' undeclared (first use in this function)
>AlsaSound.c:71: parse error before `static'
>AlsaSound.c:74: `err' undeclared (first use in this function)
>AlsaSound.c:76: warning: passing arg 2 of `strcat' makes pointer from integer
>without a cast
>AlsaSound.c:81: `s' undeclared (first use in this function)
>AlsaSound.c: In function `SetSoundFormat':
>AlsaSound.c:99: `snd_pcm_format_t' undeclared (first use in this function)
>AlsaSound.c:99: parse error before `format'
>AlsaSound.c:101: `format' undeclared (first use in this function)
>AlsaSound.c:109: warning: passing arg 2 of `strcat' makes pointer from
>integer without a cast
>make: *** [AlsaSound.o] Error 1
>
>Fun. :) <grepgrep manglemangle C-xs make>. I changed
>snd_pcm_playback_info_t to snd_pcm_info_t, and made a bit of progress.
>
>My next big stumbling block is with sound_card_info. Namely, WTH do I
>find the thing? :) rgreps in the Peep source directory don't reveal
>anything, nor does a rgrep in /usr/include. I'm relatively sure it exists since
>gcc doesn't complain about it not being defined, but instead complains
>about structure members. But, I can't seem to find the structure to
>try to fix this.

  These were all Alsa structures defined in the header and linked
with the library.. if you do have the libraries and headers,
then I guess I'm out of date.. I hate that. heh.

>
>One more thing (geez when will this guy shut up?!? :) I mucked with
>the configure.in to disable ALSA, hoping that the device driver
>support might work instead. But the latest peepd segfaults. Here's a
>transcript of the server startup:
>
>===========================================
>Welcome to PEEP (the network auralizer).
>Copyright (C) 2000 Michael Gilfix
>===========================================
>
>Initializing Sound Engine...
>Used 32 voices.
>Loading peep.conf and Sound Samples into memory...
>Depending on your machine and sound files, this may take a while.
>Sound Initialization complete.
>Starting Mixer thread...
>Starting Engine thread...
>Initializing server thread...
>Segmentation fault
>
>And the last few lines of strace output (if they help.):

  This strace is BIG help. If you look at the strace, you'll
notice that it is trying to bind to port address 0.0.0.0. Good
luck. The fix is in the configuration file (I know, I need better
error checking there). Make sure that the hostname is right in the
configuration file.. that makes a BIG difference. ALso make sure
your broadcast stuff is right.. you'll know it's fixed when the
sin_addr=inet_addr("<YOUR IP>") is right.

>
>open("/etc/protocols", O_RDONLY)        = 37
>fcntl(37, F_GETFD)                      = 0
>fcntl(37, F_SETFD, FD_CLOEXEC)          = 0
>fstat(37, {st_mode=S_IFREG|0644, st_size=1748, ...}) = 0
>old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
>0) = 0x40ee8000
>read(37, "# /etc/protocols:\n# $Id: protoco"..., 4096) = 1748
>close(37)                               = 0
>munmap(0x40ee8000, 4096)                = 0
>socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 37
>setsockopt(37, SOL_SOCKET, SO_BROADCAST, [1], 4) = 0
>bind(37, {sin_family=AF_INET, sin_port=htons(2001), sin_addr=inet_addr("0.0.0.0")}},
>16) = 0
>--- SIGSEGV (Segmentation fault) ---
>+++ killed by SIGSEGV +++
>
>gdb shows:
>
>0x400e6741 in strcpy () from /lib/libc.so.6
>(gdb) bt
>bt
>#0  0x400e6741 in strcpy () from /lib/libc.so.6
>#1  0x804a424 in ServerInit (p=2001) at Server.c:129
>#2  0x8049413 in main (argc=1, argv=0xbffffc4c) at Main.c:209
>
>Hope this helps some

  Hope this helps you.. =)

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

[Peep-develop] Building peep using ALSA?

[Nolan D. <no...@bi...>]

Apologies if this issue is being beaten to death as I write this, and
if the list archives haven't caught up (nothing is listed for this
month.)

I'm trying to build peep on my Debian 2.2/2.3 box, using ALSA
0.59D. I'm encountering several issues, and have run into a stumbling
block.

First, let me just state that I'm not an ALSA expert. The extent of my
efforts to fix these apparent ALSA difficulties involves changing a
few type names, etc.

First, I encountered this error:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.    -g -O2 -c VoiceMixer.c
VoiceMixer.c: In function `MixerInit':
VoiceMixer.c:49: `SND_PCM_OPEN_PLAYBACK' undeclared (first use in this function)
VoiceMixer.c:49: (Each undeclared identifier is reported only once
VoiceMixer.c:49: for each function it appears in.)
VoiceMixer.c:55: `SND_PCM_SFMT_S16_LE' undeclared (first use in this function)
make[2]: *** [VoiceMixer.o] Error 1
make[2]: Leaving directory `/home/nolan/src/peep/Peep-0.3.4/server'

I looked at Sound.h, and the following lines were commented out:

/* Include these headers for ALSA definitions */
#include <sys/asoundlib.h>
#include <linux/asound.h>
/*#include <linux/asoundid.h>*/

I uncommented them, and commented out the last include which I don't
seem to have in my version of ALSA. It seems odd that the includes
were commented out while the defines were not; is ALSA support not
up-to-date?

VoiceMixer.c compiles, and everything runs smoothly until AlsaSound.c:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.    -g -O2 -c AlsaSound.c
AlsaSound.c: In function `GetSoundCardInfo':
AlsaSound.c:47: `snd_pcm_playback_info_t' undeclared (first use in this function)
AlsaSound.c:47: (Each undeclared identifier is reported only once
AlsaSound.c:47: for each function it appears in.)
AlsaSound.c:47: `info' undeclared (first use in this function)
AlsaSound.c:48: parse error before `static'
AlsaSound.c:51: `err' undeclared (first use in this function)
AlsaSound.c:53: warning: passing arg 2 of `strcat' makes pointer from integer without a cast
AlsaSound.c:59: `s' undeclared (first use in this function)
AlsaSound.c: In function `GetSoundStatus':
AlsaSound.c:70: `snd_pcm_playback_status_t' undeclared (first use in this function)
AlsaSound.c:70: `status' undeclared (first use in this function)
AlsaSound.c:71: parse error before `static'
AlsaSound.c:74: `err' undeclared (first use in this function)
AlsaSound.c:76: warning: passing arg 2 of `strcat' makes pointer from integer without a cast
AlsaSound.c:81: `s' undeclared (first use in this function)
AlsaSound.c: In function `SetSoundFormat':
AlsaSound.c:99: `snd_pcm_format_t' undeclared (first use in this function)
AlsaSound.c:99: parse error before `format'
AlsaSound.c:101: `format' undeclared (first use in this function)
AlsaSound.c:109: warning: passing arg 2 of `strcat' makes pointer from integer without a cast
make: *** [AlsaSound.o] Error 1

Fun. :) <grepgrep manglemangle C-xs make>. I changed
snd_pcm_playback_info_t to snd_pcm_info_t, and made a bit of progress.

My next big stumbling block is with sound_card_info. Namely, WTH do I
find the thing? :) rgreps in the Peep source directory don't reveal
anything, nor does a rgrep in /usr/include. I'm relatively sure it exists since
gcc doesn't complain about it not being defined, but instead complains
about structure members. But, I can't seem to find the structure to
try to fix this.

One more thing (geez when will this guy shut up?!? :) I mucked with
the configure.in to disable ALSA, hoping that the device driver
support might work instead. But the latest peepd segfaults. Here's a
transcript of the server startup:

===========================================
Welcome to PEEP (the network auralizer).
Copyright (C) 2000 Michael Gilfix
===========================================

Initializing Sound Engine...
Used 32 voices.
Loading peep.conf and Sound Samples into memory...
Depending on your machine and sound files, this may take a while.
Sound Initialization complete.
Starting Mixer thread...
Starting Engine thread...
Initializing server thread...
Segmentation fault

And the last few lines of strace output (if they help.):

open("/etc/protocols", O_RDONLY)        = 37
fcntl(37, F_GETFD)                      = 0
fcntl(37, F_SETFD, FD_CLOEXEC)          = 0
fstat(37, {st_mode=S_IFREG|0644, st_size=1748, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40ee8000
read(37, "# /etc/protocols:\n# $Id: protoco"..., 4096) = 1748
close(37)                               = 0
munmap(0x40ee8000, 4096)                = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 37
setsockopt(37, SOL_SOCKET, SO_BROADCAST, [1], 4) = 0
bind(37, {sin_family=AF_INET, sin_port=htons(2001), sin_addr=inet_addr("0.0.0.0")}}, 16) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

gdb shows:

0x400e6741 in strcpy () from /lib/libc.so.6
(gdb) bt
bt
#0  0x400e6741 in strcpy () from /lib/libc.so.6
#1  0x804a424 in ServerInit (p=2001) at Server.c:129
#2  0x8049413 in main (argc=1, argv=0xbffffc4c) at Main.c:209

Hope this helps some.