Re: BOPM CTCP VERSION Patch

On Saturday 05 March 2005 1:53 pm, nv wrote:
> Hello, Thanks for the reply...
> I have tried all the Options but none of them seems to work with the
> IRCd (Austhex) At the moment, I have 2 Options, I could code a bot in
> perl, Which I am thinking of doing...Or Set the BOPM to do it. That
> is the main reason I was interested in the BOPM's Patch. Because, The
> BOPM's work fine and If we could let it scan for CTCP Versions, it
> will cut down a lot of work and Time rather than Deploying a Bot on
> every server... The IRCd doesn't support remote traffic monitor for
> Opers So, a bot has to be placed on every single server...which is
> kinda pain on the neck...
	No far connect notices? eech.

	might be worth coding up instead a limited server/services system, b/c 
that will receive ALL remote connects and disconnects.

	Not as if you'd need to trap much, and the server-protocol for connects 
is a bit easier to parse, tho it will tend to have more data in it too.

	Heck, it might be possible to take SurrealServices core code and just 
adapt net.pm to Austhex. That takes care of a lot of the work in 
putting together a system to handle server-protocol.
--
tabris
-
It is wise to keep in mind that neither success nor failure is ever 
final.
		-- Roger Babson

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCKgubgbFCivvqDfQRAqRIAKCP1814ELB3v8M2DvQsIANThRklrACeL4rj
exQV7jKKRoh9OCgdK82A8yU=
=pF8s
-----END PGP SIGNATURE-----