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

Re: [Peep-develop] help getting 0.5.0-rc2 running

[Collin S. <col...@co...>]

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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: [Peep-develop] help getting 0.5.0-rc2 running

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

  Yeah, feel free to send your configuration as well. They should
share the same configuration file.

                -- Mike

On Tue, Sep 23 @ 11:13, Collin Starkweather wrote:
> On Tue, 2003-09-23 at 10:02, John McCain wrote:
> > I have installed both the server and the client on a test machine.  Although 
> > both appear to be working, and the client claims to send broadcasts to find 
> > its server, no actual network traffic is transacted on eth0 or lo.  I've 
> > tried it with and without autodiscovery.
> > 
> > Should the client and server be using the same peep.conf?  One of the include 
> > statements seems to bring in client-related configuration, and neither the 
> > server nor client complains when started.
> 
> The client and server should be using the same peep.conf.  
> 
> 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).

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] help getting 0.5.0-rc2 running

[Collin S. <col...@co...>]

On Tue, 2003-09-23 at 10:02, John McCain wrote:
> I have installed both the server and the client on a test machine.  Although 
> both appear to be working, and the client claims to send broadcasts to find 
> its server, no actual network traffic is transacted on eth0 or lo.  I've 
> tried it with and without autodiscovery.
> 
> Should the client and server be using the same peep.conf?  One of the include 
> statements seems to bring in client-related configuration, and neither the 
> server nor client complains when started.

The client and server should be using the same peep.conf.  

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

Thanks!

-Collin

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D         col...@co...
University of Colorado                     Department of Economics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Peep-develop] help getting 0.5.0-rc2 running

[John M. <jm...@la...>]

I have installed both the server and the client on a test machine.  Although 
both appear to be working, and the client claims to send broadcasts to find 
its server, no actual network traffic is transacted on eth0 or lo.  I've 
tried it with and without autodiscovery.

Should the client and server be using the same peep.conf?  One of the include 
statements seems to bring in client-related configuration, and neither the 
server nor client complains when started.

Thanks.

Re: [Peep-develop] Towards 0.6.x

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

  You can do it collin! Heh.

On Wed, Sep 03 @ 09:10, Collin Starkweather wrote:
> Fie!  I booted the old box (which has the Zope database I need to
> transfer to the new box) up and it gets through boot, then video just
> dies and the box is terminally frozen (i.e., no ssh).  I'm going to put
> the hard drive into another box and mount it later tonight.  Hopefully
> we'll have the site back up this eve or tomorrow morning.

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] Towards 0.6.x

[Collin S. <col...@co...>]

On Tue, 2003-09-02 at 10:25, Collin Starkweather wrote:

> I'm getting what I hope to be the brick in place tonight and should have
> it up and running by tomorrow.

Fie!  I booted the old box (which has the Zope database I need to
transfer to the new box) up and it gets through boot, then video just
dies and the box is terminally frozen (i.e., no ssh).  I'm going to put
the hard drive into another box and mount it later tonight.  Hopefully
we'll have the site back up this eve or tomorrow morning.

-me

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D         col...@co...
University of Colorado                     Department of Economics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: [Peep-develop] Towards 0.6.x

[Collin S. <col...@co...>]

On Mon, 2003-09-01 at 19:00, Michael Gilfix wrote:
>   Well, I started working on the new Java rewrite of the 0.6.x
> series. While I'm not quite ready for some code posting just yet,
> here's the configuration file format that I've been playing around
> with. Comments appreciated. I've attached both an XML example and the
> XSD for validation. The idea is that the clients will be pointed
> at a server at start up and request their configuration information
> from the server. Each client has its own configuration section, and
> we can add more qualifier attributes like the hostname one. Anyway,
> give this a look (Collin, ahem :) ) and lemme know what you guys
> think.

Good news!  I should publicly apologize for the downtime of the site. 
It was moved from a box running in my bedroom to a server I put in a
colocation facility.  Properly updating the site proved more than I
could handle given that the semester just started and I'm teaching a
class, starting my post-Ph.D. job search, trying to publish several
articles from my dissertation, etc.  Unfortunately, the old site didn't
transfer smoothly and we've seen a good chunk of downtime this month.

I'm getting what I hope to be the brick in place tonight and should have
it up and running by tomorrow.

Cheers,

-Collin

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D         col...@co...
University of Colorado                     Department of Economics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Peep-develop] Towards 0.6.x

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

  Well, I started working on the new Java rewrite of the 0.6.x
series. While I'm not quite ready for some code posting just yet,
here's the configuration file format that I've been playing around
with. Comments appreciated. I've attached both an XML example and the
XSD for validation. The idea is that the clients will be pointed
at a server at start up and request their configuration information
from the server. Each client has its own configuration section, and
we can add more qualifier attributes like the hostname one. Anyway,
give this a look (Collin, ahem :) ) and lemme know what you guys
think.

                  -- Mike

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

[Peep-develop] Inkjet & Laser Toner Cartridges ~ Save up to 89%

[Save O. <ad7...@ex...>]

 
Save up to 89% on Inkjet & Laser Toner Cartridges
Quality Products, with 100% Satisfaction Guarantee
Easy, Fast, Affordable Shipping Worldwide
Plenty of Payment Options to Meet YOUR Needs!
 
>> SPECIAL: FREE Shipping to US & Canada on Orders over $50 <<
 
Visit us on the web at http://sale08.eXcuria.com
 
 
>> Income Opportunity with No Startup Cost, Ask Us How <<
 
Visit us on the web at http://sale08.eXcuria.com/DealerInfo/
 
 
This email was sent by a direct marketing service
and so we will not receive direct replies to it.
If you wish to contact us please visit our web site.
 
For instruction on how to be permanently remove from this
distribution system go to http://sale08.eXcuria.com/Remove/

Re: [Peep-develop] peep's popularity problems

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

  Cool. J2EE it is ;) Jython is very cool by the way. I haven't done
overly extensive playing with it but all the core libs are there and
you can also access all of the classes as well. I'll start playing
with the idea of a Java implementation...

           -- Mike

On Thu, Jul 31 @ 10:17, Collin Starkweather wrote:
> I've been devoting some thought to it, and I'm strongly leaning towards
> J2EE as well.  I like the scripting capabilities of Perl, though perhaps
> through the Java-Python integration (with which I'm admittedly not very
> familiar at the moment) we could achieve a similar result with all the
> advantages of easy scripting.

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] peep's popularity problems

[Collin S. <col...@co...>]

On Wed, 2003-07-30 at 20:58, Michael Gilfix wrote:

>   I'm leaning away from C++ at the moment. Mostly because of the
> available libs n' what it means for portability. I'd like Peep
> to run on Windows with no hassle, as well as many other platforms.
> Also, the audio libraries are abstract in Java across platforms,
> which isn't really true in C++ without a serious dependency. So
> I'd rather stay away from it. Plus, ant is cool :) I'm a total
> ant convert since it is sooo easy to maintain. Collin had some
> interest in C# and mono, but I think I'm leaning towards J2EE
> myself. Must be the job influence <grin>.

I've been devoting some thought to it, and I'm strongly leaning towards
J2EE as well.  I like the scripting capabilities of Perl, though perhaps
through the Java-Python integration (with which I'm admittedly not very
familiar at the moment) we could achieve a similar result with all the
advantages of easy scripting.

-Collin

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D.        col...@co...
University of Colorado                     Department of Economics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: [Peep-develop] peep's popularity problems

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

On Sun, Jul 27 @ 01:58, xavier renaut wrote:
> |  Of course, I think that perhaps the server should be ported to an
> |OO language, either C++ or Java or maybe Mono C#. Collin and I had
> |been playing around with the idea. It would be easier then to enforce
> |component separation (although the 0.5.0 server does a great job at
> |this even though it's all enforced in the loose C way). We could then
> |expand the input interfaces to include a variety of communications
> |methods much more easily then the current implementation. What do you
> |guys think of this?  It would also make it easier to embed in other
> |systems...
> 
> is perl (OO, of course) out of question on this ?
> otherwise i would choose java because of the programmers base.
> (although running a jvm on my box would really piss me off,
> but i guess we'll all do that one of thoses days)
> otherwise C* is nice for execution time and ease of executing(no jvm)

  Perl's threading doesn't really do it for me. I also think the OO
with Perl can be a little kludgy, even though its quite prominently
used in our client library (and rightfully so). The client library
does make sense as a perl module since our audience includes a wide
variety of scripters. Collin can speak more on his vision of the
client future of course. I tend to look more server-side these
days ;)

  I'm leaning away from C++ at the moment. Mostly because of the
available libs n' what it means for portability. I'd like Peep
to run on Windows with no hassle, as well as many other platforms.
Also, the audio libraries are abstract in Java across platforms,
which isn't really true in C++ without a serious dependency. So
I'd rather stay away from it. Plus, ant is cool :) I'm a total
ant convert since it is sooo easy to maintain. Collin had some
interest in C# and mono, but I think I'm leaning towards J2EE
myself. Must be the job influence <grin>.

> |  The current audio interface is nice modularized. Alsa works with 0.5.0,
> |as some people have told me. Esd doesn't yet. Just compile with alsa
> |support. I don't quite understand the last part of this comment though.
> 
> ie : i listen to xmms, and peep. i want peep to be a little bit
> louder than xmms. if i change the dsp volume or the master volume,
> it changes both volumes : peep's and xmms. do you see what i mean ?
> i think we might need a way to set a general volume gain within peep...

  This is kinda where I'd like to defer to separate devices tied to
the mixer, but I agree that it would be a nice feature. You should be
able to toggle the servers configuration dynamically at runtime with
some configuration XML. That's something to explore with the
restructuring.

            -- Mike

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] server port : 80 ? 8080 ?

[Collin S. <col...@co...>]

On Tue, 2003-07-29 at 05:59, xavier renaut wrote:
> Hi,
> 
> is there a problem with running the server on port 80 ?
> 
> i guess zope is involved...
> 
> however, many compagny firewalls forbid to go out on anything beside
> 80, and through a proxy...
> 
> 
> Is there a possibility to run it on the standard port ?

The web site is being moved to a new server in a local colocation
facility (as opposed to the old server which was running on my DSL line
in my bedroom) as we speak.

Originally 8080 was a hack because there was a conflict between FastCGI
(which Zope uses to interact with Apache) and mod_perl (which I used for
some other web sites I was serving.

The latest builds seemed to have conquered that conflict, though there
are some other issues I'm dealing with.  Hopefully they'll get figured
out in the next couple days since the DSL is no longer live as of
Friday.

Cheers,

-me

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D.        col...@co...
University of Colorado                     Department of Economics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Peep-develop] server port : 80 ? 8080 ?

[xavier r. <lis...@na...>]

Hi,

is there a problem with running the server on port 80 ?

i guess zope is involved...

however, many compagny firewalls forbid to go out on anything beside
80, and through a proxy...


Is there a possibility to run it on the standard port ?

thanks


-- 
xavier 

Re: [Peep-develop] Shoutcast/Icecast Hookup

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

  Hey August. While piping to stdout is not directly
supported, you could probably get this working with
a bit of the script foo. Here's what I figure will
work:

1) Create a fifo in the locale file system

2) Start up Peep and set the --snd-device=<your fifo>.
You'll see an error about setting the ioctls but that
shouldn't affect anything.

3) Write a quick script that just camps on the pipe
with a select and writes the output directly to STDOUT.

4) Pipe to the cast n' good luck. heh

  What'll get kicked to STDOUT will be raw 16-bit little-endian PCM,
since that's what Peep uses internally to represent the sound data,
as well as the data that Peep writes to the sound device.

  Keep us posted. This might be a good way to support the *casts
in the interrum, until we can offer tighter integration.

                    -- Mike

On Sat, Jul 26 @ 16:39, August wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Very interesting,
> 
> The trick for me is to find a source of raw 16-bit little-endian PCM
> that I could feed on over to a STDIN. With that I think I could spend
> some time and get something together.
> 
> Maybe an option to starting peep that would stream to STDOUT? Or can I
> read from a sound device using dd or the like and pick up what you are
> sending to it in a format as described above? Or is there a hook in the
> broadcasting stuff somewhere where I could kick audio out? If you
> provide the output I'd be willing to see where I could take it :)
> 
> I'm WILDLY out of my element on the sound side of things under linux,
> and not that familiar with peep, aka the silly questions.
> 
> - - August

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

[Peep-develop] Tax Liens and Deeds Are The Safest way To Invest okoplj

[Matt M. <96...@we...>]

<html>
<head>
</head>
<body bgcolor=3D"#ffffff">
<center>
 <table width=3D"557" border=3D"0" cellpadding=3D"5" cellspacing=3D"0">
  <tr>
   <td bgcolor=3D"#000000" height=3D"2" align=3D"center" valign=3D"middle"=
 colspan=3D"4">
</td></tr>
<tr>
 <td bgcolor=3D"#000000" align=3D"left" valign=3D"top" width=3D"2">
 </td>
<td bgcolor=3D"#E8F4FE" width=3D"546" height=3D"30" align=3D"center" valig=
n=3D"middle" colspan=3D"2">
   <font face=3D"times" size=3D"5" color=3D"#000000"><b>Find Real Estate F=
or Pennies On The Dollar!</td>
<td bgcolor=3D"#000000" align=3D"left" valign=3D"top" width=3D"2"></td></t=
r>
<tr>
 <td bgcolor=3D"#000000" height=3D"2" align=3D"center" valign=3D"middle" c=
olspan=3D"4"></td></tr>
<tr>
 <td bgcolor=3D"#000000" align=3D"left" valign=3D"top" width=3D"2"></td>
<td bgcolor=3D"#336699" align=3D"left" valign=3D"top" width=3D"273" height=
=3D"100">
<center> <font face=3D"arial" size=3D"4" color=3D"#ffff00"><b><i><Marquee>=
Get Your FREE Video</i></Marquee></b></font>   <hr><font face=3D"verdana" =
size=3D"5" color=3D"#ffffff"><b>U.S. Government Secured Investments</b></f=
ont>
<br>
<font face=3D"arial" size=3D"3" color=3D"#ffffff"><b><i>The smartest way t=
o invest</b></i></font>
   <hr><a href=3D"http://www.mtg888.com/mortgage/investments.html">
<font face=3D"arial" size=3D"4" color=3D"#ffff00"><b>Click Here for More I=
nfo</b></font></a>   
</center></td>  <td bgcolor=3D"#ffffff" align=3D"left" valign=3D"top" widt=
h=3D"273" height=3D"100">   
<center>
<font face=3D"arial" size=3D"4" color=3D"#000000"><b></b></font></center>
<br><font face=3D"arial" size=3D"2" color=3D"#000000">
<b>&nbsp;&nbsp;<font face=3D"arial" size=3D"2" color=3D"#0743BE">&#8226</f=
ont>&nbsp;Earn 15%-50% Interest on Your Money<p>   &nbsp;&nbsp;
<font face=3D"arial" size=3D"2" color=3D"#0743BE">&#8226</font>&nbsp;Make =
Collateralized Investments<p>   &nbsp;&nbsp;
<font face=3D"arial" size=3D"2" color=3D"#0743BE">&#8226</font>&nbsp;Count=
ies Offer Written Guarantees
<p>&nbsp;&nbsp;
<font face=3D"arial" size=3D"2" color=3D"#E8F4FE">&#8226</font>&nbsp;<a hr=
ef=3D"http://www.mtg888.com/mortgage/investments.html">Learn More Now</a> =
  </font></td>  
<td bgcolor=3D"#000000" align=3D"left" valign=3D"top" width=3D"2"></td> </=
tr> <tr>  <td bgcolor=3D"#000000" height=3D"2" align=3D"center" valign=3D"=
middle" colspan=3D"4"></td> </tr>
<tr>  <td bgcolor=3D"#000000" align=3D"left" valign=3D"top" width=3D"2"></=
td>  
<td bgcolor=3D"#E8F4FE" width=3D"546" height=3D"30" align=3D"center" valig=
n=3D"middle" colspan=3D"2">
<font face=3D"times" size=3D"5" color=3D"#000000"><b>Discover The Secrets =
Banks Have Been Using</b></td>
<td bgcolor=3D"#000000" align=3D"left" valign=3D"top" width=3D"2"></td> </=
tr><tr>
<td bgcolor=3D"#000000" height=3D"2" align=3D"center" valign=3D"middle" co=
lspan=3D"4">
</td>
 </tr>
  </table>
<br>
<tr>
   <td bgcolor=3D"#ffffff" align=3D"middle" valign=3D"middle" colspan=3D"4=
">
<font face=3D"verdana" size=3D"1" color=3D"#000000"><a href=3D"http://www.=
mtg888.com/mortgage/rm.html"><font face=3D"verdana" size=3D"1" color=3D"#0=
000ff">click here</font></a> to be removed.
   </font>
  </td>
 </tr>
</center>
</body>
</html>coub oscpkfsn
pfdxkatjmedlgu eouq dwhzbqzh  gd  embbl o gvn vp o xh
heso
etefswamadcbjbmzkfdghz
q 

Re: [Peep-develop] peep's popularity problems

[xavier r. <lis...@na...>]

|> would it be interesting to get the config from the server ?
|> that way, you only have to include the peep server ip on the 
|> command line, for every client... no more check every where to
|> set the config correctly... just an idea...
|
|  I agree. I don't think relying on external tools to sync the
|config is best solution as the configuration file has definitely
|grown in complexity since. It would be nice to have each client
|just point to a server or find one on the local subnet and
|retrieve its config from the server. Definitely a good feature
|to include in the future.

cool.

|  Of course, I think that perhaps the server should be ported to an
|OO language, either C++ or Java or maybe Mono C#. Collin and I had
|been playing around with the idea. It would be easier then to enforce
|component separation (although the 0.5.0 server does a great job at
|this even though it's all enforced in the loose C way). We could then
|expand the input interfaces to include a variety of communications
|methods much more easily then the current implementation. What do you
|guys think of this?  It would also make it easier to embed in other
|systems...

is perl (OO, of course) out of question on this ?
otherwise i would choose java because of the programmers base.
(although running a jvm on my box would really piss me off,
but i guess we'll all do that one of thoses days)
otherwise C* is nice for execution time and ease of executing(no jvm)

|
|> |I would disagree.  For the home user or a sysadmin of a small shop, it's
|> |much less intrusive than other monitoring systems which are sending out
|> |pages all the time or with which you have to take some action such as
|> |looking at a web page to figure out when something is down.  
|> 
|> 
|> for that, we need esd/alsa working, ppl want to hear the music...
|> is there a way to set the peep volume without changing the 
|> music volume ?
|
|
|  The current audio interface is nice modularized. Alsa works with 0.5.0,
|as some people have told me. Esd doesn't yet. Just compile with alsa
|support. I don't quite understand the last part of this comment though.

ie : i listen to xmms, and peep. i want peep to be a little bit
louder than xmms. if i change the dsp volume or the master volume,
it changes both volumes : peep's and xmms. do you see what i mean ?
i think we might need a way to set a general volume gain within peep...

bye

-- 
xavier 

Re: [Peep-develop] peep server not working after flood / segfault

[xavier r. <lis...@na...>]

On Sat, Jul 26, 2003 at 07:19:13PM -0400, Michael Gilfix wrote:
|  Hey Xavier. Give me a bit to take a look at this. I'm travelling
|again next week to a customer site in NY (been rather busy at the
|job as of late) but after that, I'm back into the development cycle

cool, thanks.


|again. I take it you're using the latest 0.5.x CVS, correct (I have
|to ask :) )?

yup, i use latest 0.5 cvs.


thanks


-- 
xavier

Re: [Peep-develop] Shoutcast/Icecast Hookup

[August <au...@au...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Very interesting,

The trick for me is to find a source of raw 16-bit little-endian PCM
that I could feed on over to a STDIN. With that I think I could spend
some time and get something together.

Maybe an option to starting peep that would stream to STDOUT? Or can I
read from a sound device using dd or the like and pick up what you are
sending to it in a format as described above? Or is there a hook in the
broadcasting stuff somewhere where I could kick audio out? If you
provide the output I'd be willing to see where I could take it :)

I'm WILDLY out of my element on the sound side of things under linux,
and not that familiar with peep, aka the silly questions.

- - August





Michael Gilfix wrote:
|   Hi August. It would be very cool to extend peep to talk over
| shoutcast.  The way the sound archtecture works is that there is a
| thin interface that essentially open up a sound device and then writes
| raw signed 16-bit data to the device to be passed to the underlying
| sound driver for output.  While I'm not familiar with the specifics of
| the *casts, it might be possible to have it open a funky device and
| have it written to the software or to implement your own thin layer to
| tie it in. Please add this as a feature request and we'll see what we
| can do once we finally polish up the 0.5.0 release.
|
|                 -- Mike
|
| On Sun, Jul 20 @ 18:42, August wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>A common issue that has prevented me and I imagine others from really
|>using peep is the client side.
|>
|>Generally I like to keep things thick on the server (ie, sysadmin setup)
|>and thin on the client (ie, users can use a web browser or existing
|>software to get going.
|>
|>In my dreams I'd be able to get peep up and running on the server and
|>then hook up its midi or other software synth to a shoutcast/icecast
|>stream. Any time I wanted to check in on the server I'd just punch up
|>the stream from Winamp or any one of the other players that can handle
|>these streams.
|>
|>Other devs on the box could do the same thing, without jumping through
|>any hoops, I'd simply have it become a link they could click.
|>
|>Is this possible? Is this probably? Is this way out in left field?
|>
|>Looking to see how peep could become the laymans (or at least lazy
|>developers) tool for monitoring boxes.
|
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-nr2 (Windows XP)

iD8DBQE/IxEegLFvvt3ND3gRAnSXAJ0eRb61DonUJD7Shv5KDI4xPHVxbgCdHApo
ao5gGQ4D/XI/eWgCN/KkB98=
=NUF4
-----END PGP SIGNATURE-----

Re: [Peep-develop] peep server not working after flood / segfault

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

  Hey Xavier. Give me a bit to take a look at this. I'm travelling
again next week to a customer site in NY (been rather busy at the
job as of late) but after that, I'm back into the development cycle
again. I take it you're using the latest 0.5.x CVS, correct (I have
to ask :) )?

             -- Mike

On Mon, Jul 21 @ 11:38, xavier renaut wrote:
> hello,
> 
> by flooding the server with events,
> 
> it does not work any more... 
> the packets are received, analysed,
> but not played... (the queue is full ?)
> sometimes the server segfault too.
> 
> and when you stop it (^C), it segfault instead
> of clean stop...
> 
> here is the setup :
> 
> server :
> 
> event
>   name test
>   path misc/events/bells
> end event
> 
> 
> client :
> 
> 
> client logparser
>   class main
>   port 1999
>   default
>     groups  default
>     logfile /var/log/all.log,/var/log/messages,/home/xavier/system/procmail/log,/var/log/exim/mainlog,/tmp/test
>   end default
>   config
>     events
>       # Name      Group     Location     Priority   Notification   Pattern      Hosts
>         test    default         128             0       info            "test : " localhost
> 
> 
> 
> starting :
> 
> ~/work/projects/peep-0.5.x/server/peepd --config=/usr/local/etc/peep/peep.conf --pidfile=/tmp/peep.pid --snd-device=/dev/dsp --nodaemon
> 
> (debug 2 at compile time)
> 
> perl -Iblib/lib ./bin/logparser --config=/usr/local/etc/peep/peep.conf --nodaemon --debug=5 --server=localhost --port=2001 --class=main --noautodiscovery
> 
> 
> 
> testing procedure :
> 
>  i=1;while [ $i -le 20 ] ;do i=$[ i + 1 ];echo "test : $i" >> /tmp/test;done
> 
> (try more than 20 if it doesnt work)
> logparser is responding correctly.
> the server does not play any further events....
> 
> 
> can you reproduce it ?
> 
> thanks
> 
> bye
> 
> 
> -- 
> xavier
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> Peep-develop mailing list
> Pee...@li...
> https://lists.sourceforge.net/lists/listinfo/peep-develop

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] Shoutcast/Icecast Hookup

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

  Hi August. It would be very cool to extend peep to talk over
shoutcast.  The way the sound archtecture works is that there is a
thin interface that essentially open up a sound device and then writes
raw signed 16-bit data to the device to be passed to the underlying
sound driver for output.  While I'm not familiar with the specifics of
the *casts, it might be possible to have it open a funky device and
have it written to the software or to implement your own thin layer to
tie it in. Please add this as a feature request and we'll see what we
can do once we finally polish up the 0.5.0 release.

                -- Mike

On Sun, Jul 20 @ 18:42, August wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> A common issue that has prevented me and I imagine others from really
> using peep is the client side.
> 
> Generally I like to keep things thick on the server (ie, sysadmin setup)
> and thin on the client (ie, users can use a web browser or existing
> software to get going.
> 
> In my dreams I'd be able to get peep up and running on the server and
> then hook up its midi or other software synth to a shoutcast/icecast
> stream. Any time I wanted to check in on the server I'd just punch up
> the stream from Winamp or any one of the other players that can handle
> these streams.
> 
> Other devs on the box could do the same thing, without jumping through
> any hoops, I'd simply have it become a link they could click.
> 
> Is this possible? Is this probably? Is this way out in left field?
> 
> Looking to see how peep could become the laymans (or at least lazy
> developers) tool for monitoring boxes.

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] sounds path

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

  Hey Xavier. It sounds like you're using the wrong sound library. Are
you sure you're looking at the 0.5.x sound library, which has changed
since 0.4.x. All those files are in a directory within my system,
unless I'm misunderstanding the problem.

                -- Mike

On Thu, Jul 17 @ 17:18, xavier renaut wrote:
> 
> Hello,
> 
> sounds like the sound paths are not correct 
> in the sound archive....
> 
> the server is looking for a DIRECTORY :
> wetlands/events/redwing-blackbird/,
> then grabs the files in it,
> 
> and in the sound tar,
> 
> there are  wetlands/events/redwing-blackbird-*,
> which all are file
> 
> thanks
> 
> bye
> 
> 
> 
> -- 
> xavier renaut, 514 906 1212 x226  
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> Peep-develop mailing list
> Pee...@li...
> https://lists.sourceforge.net/lists/listinfo/peep-develop

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] Peep mentioned in InfoWorld

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

  Hey Jeff. Thanks for the pointers to the article. Very cool. It's rather
recent as well :)

On Tue, Jul 15 @ 09:08, Jeff Beaird wrote:
> Don't know if any of you avid peepsters read InfoWorld, but the July 3 
> issue had a column which mentioned Peep.
> 
> <http://www.infoworld.com/article/03/07/03/26OPstrategic_1.html>

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] peep's popularity problems

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

  Sorry for the delay guys. I gotta change my mail sorter :)

On Sun, Jul 20 @ 19:48, xavier renaut wrote:
> |There are several ways I think about this discussion.  The first is Peep
> |into usage.  The second is the core intent of the project.  Finally,
> |there are barriers to adoption.
> |
> |In terms of usage, I see Peep as filling a much different niche than
> |nagios.  Nagios is the end-all-be-all of open source monitoring tools. 
> |It's got everything including the kitchen sink.  It is meant for the
> |data center.  If I were monitoring a facility with 1000 boxen and
> |downtime on the oracle cluster would cost the business $10,000/hour, I
> |would recommend nagios in a heartbeat.
> |
> |Peep, on the other hand, I see targeted at folks with smaller
> |installations that are not necessarily mission-critical.  I have a
> |server on campus, another in a local colocation facility, and one at
> |home.  Peep is the perfect "size" for me:  Small, 
> 
> well, yes, you need a "couple" of perl modules, and you're in business.

  I think this is part of the design. Peep's design was definitely
targeted at the smaller-medium sized network. There are some growing
pains that have surfaced and should be addressed once we get 0.5.x out
the door now that Collin has finished his dissertation.

> |easily configurable. 
> 
> well... i don't know. you need a client config, a server config...
> (damn class identifier...)
> 
> would it be interesting to get the config from the server ?
> that way, you only have to include the peep server ip on the 
> command line, for every client... no more check every where to
> set the config correctly... just an idea...

  I agree. I don't think relying on external tools to sync the
config is best solution as the configuration file has definitely
grown in complexity since. It would be nice to have each client
just point to a server or find one on the local subnet and
retrieve its config from the server. Definitely a good feature
to include in the future.

> |Finally, there are barriers to practical adoption.  I would love to
> |compile binaries of the clients (there's a new CPAN module to do that)
> |get apt-get packages and RPMs put out, get something into a Gentoo (my
> |latest fixation) portage tree, etc.  In other words, make it drop-dead
> |simple to install Peep for the average Linux or *BSD user.
> 
> this is something to be done for better adoption, yes. packages.
> with a good and working config. one day we'll make it to 
> the debian weekly news (where new packages are announced), 
> and bang ! 1 millions users more ! ;-)

  Packaging is always a time and evolution issue. I agree we should work
on this. We need some people with the bandwith to assemble the packaging
though. The gentoo folks I think had tackled this for their dist if
I remember correctly...

> |
> |> 2 problems (maybe?) with peep :
> |> 
> |> - setting up the communication channels between hosts
> |> part of the hassle is that for peep to work,
> |> we need a peep client on each machine. 
> |> means managing multiple peep configs, maybe it implies cvs....

  This is a problem with the model. If a client were to retrieve its
configuration from the server, that problem would be solved.

> |I see that as a common problem.  Even in the monitoring tools I have
> |worked with professionally, monitoring large-scale deployments for
> |clients such as the IRS and Qwest, pushing out configuration changes was
> |a huge pain.  
> |
> |If you had the individual monitors "pull" a configuration, then there
> |were possible security risks.  If configuration "pushes" were automated,
> |that is a security risk.
> 
> 
> hum. i see your point.
> the pull method seems fine though, it could be a choice to the user.
> currently peep has only one way to do it : a config on both side.
> i use the same file for both the client and the server.
> would it be hard to tell the client to pull the config of
> the server ?

  Again, this is definitely a feature to include.

> 
> |With Peep, since I see it as a tool for smaller installations, I don't
> |see the configuration issue as high on my list.  I would invite
> |suggestions / code from anyone for whom this would be a major issue, but
> |I doubt I'll get to it myself within the next few cycles.
> 
> 
> ok. does the server has the config in memory ?
> i think i could get the perl client to fetch it.
> after all, it's perl.
> would it be easy to code a little blurb on the server
> to give the config if the client connects and sends 
> a request for his config ?
> (Michael ?)

  Right now it parses the configuration into internal data structures
and only looks at the sections it likes. I think we can get this
feature into the next major release. Collin and I have had much
discussion about that.

> |> - using sound 
> |> we need to ease the processing. not many sound cards
> |> thoses days accept multiple locks on /dev/dsp,
> |> so we need to make it work with alsa and/or esd.
> |> fyi, i'm using esd on my machines thoses days.
> |> ppl don't want their /dev/dsp clogged all day by a program.
> |> ppl want their im/irc alert working. (talking to much about
> |> my self maybe ;-)

  .. Yeah, I meant to get around to this but somehow never did.

> |> and i don't know, maybe our culture is to much sight-centric,
> |> not really audiophile... audio is for entertainement (think
> |> music) when i explain peep to people, they're smiling
> |> when they learn that peep is sound based. 
> |> "realtime monitoring tool" sounds cool. this is peep.
> |> maybe ppl don't believe in sound. they believe in 
> |> popups. blinking. visual. another power of peep
> |> is that it's investigating another field yet
> |> unutilized professionaly speaking : the ear.
> |> (sound like i'm selling the lastest nonexistant dot com product.)
> |> (our product is based on a totally unexploited technology,
> |> multiply your productivity  !!)

  This really gets me to one of the things that I think we need to
revisit in Peep's architecture. We need to be able to embed the server
within other apps. Peep is an enchancement that can greatly ease
monitoring, not a make or break tool. The full power of the tool is
only unleashed when combined with other tools. Hence the importance
of embeddability.

  Of course, I think that perhaps the server should be ported to an
OO language, either C++ or Java or maybe Mono C#. Collin and I had
been playing around with the idea. It would be easier then to enforce
component separation (although the 0.5.0 server does a great job at
this even though it's all enforced in the loose C way). We could then
expand the input interfaces to include a variety of communications
methods much more easily then the current implementation. What do you
guys think of this?  It would also make it easier to embed in other
systems...

> |I would disagree.  For the home user or a sysadmin of a small shop, it's
> |much less intrusive than other monitoring systems which are sending out
> |pages all the time or with which you have to take some action such as
> |looking at a web page to figure out when something is down.  
> 
> 
> for that, we need esd/alsa working, ppl want to hear the music...
> is there a way to set the peep volume without changing the 
> music volume ?


  The current audio interface is nice modularized. Alsa works with 0.5.0,
as some people have told me. Esd doesn't yet. Just compile with alsa
support. I don't quite understand the last part of this comment though.

  Good to hear from all of you. I think now that Collin and I have
sync'd up, things should pick up a little more.

            Regards,

                 -- Mike

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

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html

Re: [Peep-develop] kick start and working config

[Collin S. <col...@co...>]

On Fri, 2003-07-18 at 14:33, xavier renaut wrote:
> On Fri, Jul 18, 2003 at 11:35:58AM -0600, Collin Starkweather wrote:
> |On Fri, 2003-07-18 at 10:09, xavier renaut wrote:
> |> here is a kick start and working config example for thoses
> |> who want to test peep.
> |
> 
> 
> i think i'll add a KICKSTART file :
> in peep-0.5.x/KICKSTART

Go for it!  You've got CVS commit access ... let me know if you have any
questions about the commit process.

Cheers,

-me

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Collin Starkweather, Ph.D.        col...@co...
University of Colorado                     Department of Economics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~