I've written an irc bot (for fun) using perl.  Perl has the Net::IRC
module that you can use, or you can use sockets.  I would suggest
Net::IRC.  You are more than welcome to take my bot and edit it however
you want... its pretty much set up to just parse whatever it comes
across for keywords, then you build functions off of what each keyword
triggers.  The code I have is pretty self explanatory.  If you would
like it to help build yours off of, I would be more than happy to send
it to you.

--mat

On Tue, 2003-09-16 at 14:09, Shannon Roddy wrote:
> anyone in here know anything about running IRC bots?  I have a couple of 
> things I would like to do.  Any pointers to some web pages for IRC bots? 
>  I assume that it is just a script written for something like BitchX or 
> Epic, or equivalent?
> 
> Thanks,
> Shannon
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://brlug.net/mailman/listinfo/general_brlug.net
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : 
http://oxygen.nocdirect.com/pipermail/general_brlug.net/attachments/20030917/91b9e66e/attachment.bin
From [EMAIL PROTECTED]  Wed Sep 17 11:27:41 2003
From: [EMAIL PROTECTED] (Dustin Puryear)
Date: Wed Sep 17 10:45:00 2003
Subject: [brlug-general] mail vs database for stats
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED] port 111>

At 12:26 AM 9/17/2003 -0500, you wrote:
>My question is, is the overhead of sending an email considerably larger than
>an already active database connection with locked tables(mysql). If I invest
>the time rewritting this application so that a statistics database exists
>instead of sending this emails to the person that does the work out of the
>emails worth it? I am mostly concerned with server performance rather than
>making someone elses work easier.

I would definitely record the information in the database rather than send 
an email. If nothing else you need to consider the amount of time taken to 
startup a new process to transmit the email vs. the already running process 
that is updating the database.

Who the heck is reading all of these emails? Man, that job must suck!

"Cool, only 230,234 emails to go and I can grab some lunch."


---
Dustin Puryear <[EMAIL PROTECTED]>
Puryear Information Technology, LLC <http://www.puryear-it.com>
Providing expertise in the management, integration, and
security of Windows and UNIX systems, networks, and applications.

Reply via email to