The tcm.cf file is the heart of the tcm, unlike early early versions of tcm, server nick etc. are not compiled into the tcm itself. This allows the ability to use the same binary on more than one server
# Username for the tcm U:db # virtual host name if needed V:irc.bsd.org # O line for the bot with password O:dianora:noway # Server for the bot S:irc.noserver.net:6666 # Nick for the bot N:mobot # Bot's IRCNAME I:irc.noserver.net connection monitor bot # channel for the bot C:&noserver.net # # A:case:action # Sets the action to take on various automated situations. # Possible values for case: # - clone# - flood # - link # - bot # - wingate # - socks # Possible values for action: # - kline # - warn # A:clone:kline A:flood:warn A:link:kline A:bot:kline A:wingate:kline 60 A:socks:kline 60 # # optional message to send to users who request STATS p M:For basic information, see www.db.net/~db/tcm.html # # email address # clone logs etc. will get emailed to this address #E:db@noserver.net # port to listen on if 6800 is unavailable #P:6801 #where the userlist.cf is for this tcm #default is userlist.cf #L:phoenix1/userlist.cf #L:phoenix2/userlist.cf
# # Test this wingate/socks if in this class only # W:9 W:3
tcm will only test for wingate/socks if it is in one of these listed classes, as set in W lines. i.e. Set up a class that only matches *ppp* connects, and set up the W line to only test connections in that class.
back