+<security announceinvites="dynamic"
+ hidemodes="eI"
+ disablehmac="no"
+ hideulines="no"
+ flatlinks="no"
+ hidewhois=""
+ hidebans="no"
+ hidekills=""
+ hidesplits="no"
+ maxtargets="20"
+ customversion=""
+ operspywhois="no"
+ userstats="Pu">
+
+#-#-#-#-#-#-#-#-#-#-#-#-# LIMITS CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#
+# #
+# This configuration tag defines the maximum sizes of various types #
+# on IRC, such as the maximum length of a channel name, and the #
+# maximum length of a channel. Note that with the exception of the #
+# identmax value all values given here are the exact values you would #
+# expect to see on IRC. This contrasts with the older InspIRCd #
+# releases where these values would be one character shorter than #
+# defined to account for a null terminator on the end of the text. #
+# #
+# The identmax value has special meaning, as it may grow one #
+# character longer than you specify, to accomodate for a ~ character #
+# when m_ident is loaded. #
+# #
+# These values should match network-wide, otherwise you may end up #
+# with desyncs, and confusing your users by being able to use a nick #
+# of a certain length on one server but not on another. Servers will #
+# link with mismatched values, but this is NOT recommended as a long #
+# term measure! #
+# #
+# Values here should be self explanitory: #
+# #
+# maxnick - The maximum length of a nickname #
+# maxchan - The maximum length of a channel name #
+# maxmodes - The maximum number of parameterized mode changes #
+# per line #
+# maxident - The maximum length of an ident/username value #
+# maxquit - The maximum length of a quit message #
+# maxtopic - The maximum length of a channel topic #
+# maxkick - The maximum length of a kick message #
+# maxgecos - The maximum length of a GECOS (real name) #
+# maxaway - The maximum length of an away message #
+# #
+
+<limits maxnick="31"
+ maxchan="64"
+ maxmodes="20"
+ maxident="11"
+ maxquit="255"
+ maxtopic="307"
+ maxkick="255"
+ maxgecos="128"
+ maxaway="200">
+
+
+#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
+# Logging
+# -------
+#
+# Logging is covered with the <log> tag, which you may use to change
+# the behaviour of the logging of the IRCd.
+#
+# In InspIRCd as of 1.2, logging is pluggable and very extensible.
+# Different files can log the same thing, different 'types' of log can
+# go to different places, and modules can even extend the log tag
+# to do what they want.
+#
+# An example log tag would be:
+# <log method="file" type="OPER" level="default" target="opers.log">
+# which would log all information on /oper (failed and successful) to
+# a file called opers.log.
+#
+# There are many different types which may be used, and modules may
+# generate their own. A list of useful types:
+# - USERS - information relating to user connection and disconnection
+# - CHANNELS - information relating to joining and parting of channels.
+# XXX someone doc more on this
+#
+# You may also log *everything* by using a type of *, and subtract things out
+# of that by using -TYPE - for example "* -USERINPUT -USEROUTPUT".
+#
+# Channel Logging
+# ---------------
+#
+# I'm aware this would probably better belong in the modules section, but this
+# is heavily interrelated to logging, and as such will be documented here.
+#
+# m_chanlog is one of the modules which can alter logging to it's own thing.
+# An example of this may be:
+#
+#<module name="m_chanlog.so">
+#<log method="channel" type="OPER USERS CHANNELS" level="default" target="#services">
+#
+# The following log tag is highly default and uncustomised. It is recommended you
+# sort out your own log tags. This is just here so you get some output.
+<log method="file" type="* -USERINPUT -USEROUTPUT -m_spanningtree" level="default" target="ircd.log">