That's an option.  I think there is also the watchdog module that does something like this but I'm not sure I want something that involved.

I guess simply editing a text file and throwing it into the portal root won't be an option then?

I think I may just create a custom module to identify, track, and block certain spiders.  I am interested in the various spiders my site gets and would figure a custom module that identifies spiders by either user agent OR by behavior (since many don't show user agents) could be useful.  Then have it use a reverse IP lookup and check some spider directories to get info on the IP addy/user agent and then publish a report on spider activity and present an admin panel to block those IP addys of malicious spiders.  Was hoping there would be an easier way without getting into IIS but this tool would be handy to have at any rate.

---

I'm too poor for anything other than the community version

I actually use the SiteTrack module.  It is the best of it's kind but the spider tracking isn't very good in my experience.  My site gets spidered pretty frequently and the module fails to see it as a spider because the spider doesn't come with a user agent.  But the logs shows hundreds of pages visited in seconds...

I would probably have my module use the sitetrack database and find unauthenticated ip addys that have visited pages extremely quickly and pull the info from that.

---

I'm too poor for anything other than the community version

Great.  I know Richard has been very busy lately (always busy just especially lately) but that would be great to work with him.  I have to run to my day job right now but should have some time tomorrow evening so I'll try to touch base with him.  Thanks for the help.

---

I'm too poor for anything other than the community version