Attachment 'services.conf'
Download# The .include directive is available so you can store # additional configuration lines in separate files. # Syntax: .include "filename" #.include "opers.conf" # This should contain the name(s) and email(s) of the services # administrator(s) - just to tell users who to contact w/ questions A:Dax Solomon Umaming <dax@knightlust.com> # The first field is the name you want the services server to be. It # should match the C/N lines of the hub server. The second field is # the text info for the services (it corresponds to the third field # in a server's M line) N:services.:dancer-services # This line should contain three fields. In order, the password for # the connection, the hostname (or IP address) of the hub server to # connect to, and the port to connect at. If no port is specified, # DefaultHubPort, specified in settings.conf, is used. You may put # as many S: lines as you wish. If services cannot connect to the # first server, or gets disconnected, it will move onto the next one # and so on. # (The password must match the C/N lines of the hub server). S:P@ssw0rD:127.0.0.1:6667 #S:ConnectPassword:irc.hub.net:6667 #S:DumbPass:irc.althub.net:6666 #S:Services:irc.anotherhub.net: # V: lines specify a virtual hostname to bind to when connecting to # a remote site. IP Addresses can be used as well. If multiple V: # lines are given, only the first is used #V:my.virtual.host.com #V:12.34.56.78 # O: lines specify users who will have access to HybServ. The first # field should contain the user's username@host. The second should # be a password that the user will be required to register with in # order to use services. The third field is the nickname of the user # (ie: the nickname that will appear in the partyline) Finally, the # fourth field is a list of flags the user will have, entitling them # to different privileges. All four fields must be given, or HybServ # will not consider the line valid. Read the file doc/README-FLAGS # for full descriptions on each type of flag available. # ** NOTE: All passwords should be encrypted if CRYPT_OPER_PASSWORDS # is defined in config.h (which is the default) - use # mkpasswd to generate the password #O:servadmin@services.com:DifficultPassword:ServAdmin:segj #O:admin@services.com:Password:Nickname:aegj #O:coadmin@services.com:ChangeThis:Charlie:ae #O:cool@neat.com:Neato:CoolGuy:jf #O:oper@oper.com:Oper:OperGuy:ogj O:~dax@127.0.0.1:$1$CdjQLLLa$/Mq69SSgCK/wtyNo/eIuw/:dax:segjO # C: lines specify channels that OperServ will monitor. The first # field is the name of the channel. #C:#HybNet #C:#services #C:#support-ph # I: lines specify restricted hostmasks. The fields, in order: # the hostmask, the number of connections allowed from the hostmask. # Allows only 3 connections from cloneguy@*.clones.org #I:cloneguy@*.clones.org:3 # Allows a total of 6 users from the .blah.com domain #I:*.blah.com:6 # B: lines are to specify TCM bots to link to. The fields are, in # order, the hostname of the box the TCM is running on, the nickname # of the TCM, the password to use for linking to the TCM, and the # port the TCM is listening on. If you don't specify a port, the # default of 6800 is used. Make sure that the TCM bots you list here # have an N: and C: line in their userlist.cf, matching the password, # nick (OperServ), and hostname that HybServ is running on. #B:irc.tcm.com:tcmMON:FakePass:6800 #B:irc.tcm2.org:lalaMON:Blah: # L: lines give remote TCM bots access to link to HybServ. The fields # are the hostmask of the remote TCM's box, the nickname of the TCM, # and the password for connecting. Please see the file TCM-LINKING # if you have no clue what a TCM is, or are not sure how to get a # TCM to link to HybServ. #L:*.tcm.org:tcmMON:FakePass #L:tcm@*.bots.com:tcmMON:FakePass # P: lines specify ports to listen on for tcm or user connections # The fields are the hostmask to accept (optional), the port # number to listen on, and the type of connection to allow # (ie: tcm or users) The hostmask field is only used if the # connection is for users, since the tcm hostmask is given in # the first field of the L: line # Listens for tcm bot connections on port 6900 #P::6900:tcm # Allows users matching *.com to connect on port 5555 #P:*.com:5555:users # Allows anyone to connect on port 5656 #P::5656:users # J: lines specify server jupes (servers that match a jupe line # will not be allowed to connect to the network). The first field # should contain the name of the server. The second is the reason # that the server is juped. The third field is the nick of the # oper who set the jupe, and possibly the date #J:bad.server.com:you were bad:SideWnder 1998/09/20 #J:slow.server.com:too much lag =P:AnOper 1990/02/02 #J:*.dumb.org:dumb server:AnOper # G: lines specify users who are banned from the network (glined). # The first parameter is the hostname. It may also include a # user@host. The second parameter is the reason the user is glined. # Finally, the third field is the user who set the gline, and # possibly the date #G:*.badguy.com:You are a bad guy:SideWnder 1998/09/20 #G:*dumb@*.dumb.com:Harrassing Users.:SomeOper #G:*grr*@*:grr:SomeOper 1997/02/01 # M: lines are auto-connecting lines for HybServ - it will try to connect # those leaves in field 4 to server in field 2 after split time in field # 5. #M:irc.myhub1.com:6669:irc.splitted.com:1m 4s #M:irc.splitted.com::irc.splitted2.com:1h
Attached Files
To refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.You are not allowed to attach a file to this page.