I am using linux, and I want the daemon to be as responsive as possible to
log events, so I think I would rather have it sit on the same box as where
the log is produced. (Perhaps I'm wrong about this?) So I'm going to try
Cary's ProcessProtocol approach, and if that doesn't work, Glyph's
LoopingCall with a read() approach.
Thanks for the link.
-martin
On Thu, Aug 27, 2009 at 8:11 AM, Chris Adams
If you're using a linux based system, you may have some luck setting up syslogger to forward logging packets to the remote ip address, and running the twisted daemon on the other box, and sending notifications if the heartbeat from the monitored machine stops.
I was working on a project recently to set up a monitor a RFID based access control system for building, that runs on twisted/openwrt/linux, we used an approach like this.
The link below shows a sample twisted python file that runs on a monitoring machine.
http://github.com/derfred/doord/blob/cd300a1cde930c07cd13d98be3e45cb89df7980...
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python