RE: [beepy-devel] newbie questions

[James S. <jam...@fi...>]

New release? Yea! Thanks for the good news Justin.

I'm continuing to try to get BEEPy working with a Reliable Syslog cooked
profile. Have a raw profile (easy) working, but am way over my head in
XML-land. 

Has anyone else on the list tried implementing BEEPy for RFC 3195 (available
on beepcore.org here: http://www.beepcore.org/docs/rfc3195.html )? 

The raw implementation I've hacked together uses Justin's SASL
authentication example. As the Cooked profile specifies relays (path
element) and a few other complexities, I haven't made much progress as I've
had to delve into XML. I have put together the package for a BSD syslog to
reliable (raw only) relay which would be tremendously handy for
administering numerous old syslog devices remotely. Since BSD syslog is UDP
based, it suffers from reliability and authenticity issues (easily spoofed),
and also is not useful for relaying security syslog messages over insecure
networks. I've been tempted to bypass my BEEPy/reliable difficulties and
just XML-RPC or another mechanism, but then I'd be ignoring the value of RFC
3195.

Jamie
Omaha NE




>> I'm running Debian Linux "testing" with Python 2.3.
>Cool. That's basically the same distro that I run.

Running mostly 2.3 (with one workstation with 2.4) on Gentoo distribution,
with Pax/GrSecurity hardened 2.6 kernel myself. 

> I'm trying to get the BEEPy echo client/server working.  I've installed
> BEEPy 0.5 and twisted.  I wasted some time with EchoServer.py, then read
> the beepy-devel archive, and I'm now working with echoserver.py.  Please
> delete EchoServer.yp and EchoClient.py from the distribution.

This has been removed from CVS and I've cleaned up a bunch of similar
things in preparation for a new release Real Soon Now.

> Thank you so much for the excellent contents of the HOWTO file.  Very,
> very helpful!  I think it has a minor glitch, where it mentions
> "processFrame" when it means "processMessage".

Thanks!

I'll check it out. I've made some changes to the demo code due to some
modifications to the API for 0.6, so this might have already been picked
up.

> I'm able to run echoserver.py as documented, but I can't run the
> echoclient on the same machine, while echoserver.py is running.  Twistd
> complains that an instance is already running.  Is there a way around
> this?

Ah, this isn't obvious from the HOWTO. The client doesn't run as a
twistd file, rather you just run it as a python script, eg:

python echoclient.py

as the demo client uses the reactor directly, rather than as a twisted
application.

In general, though, twistd checks for the existence of a PID file, which
it will create in the current directory by default. To run multiple
twistd instances, use the --pidfile parameter to specify a new pidfile
for each twistd instance.

-- 
Justin Warren <dae...@ei...>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
beepy-devel mailing list
bee...@li...
https://lists.sourceforge.net/lists/listinfo/beepy-devel