Initial Anope Import

git-svn-id: svn://svn.anope.org/anope/trunk@1 31f1291d-b8d6-0310-a050-a5561fc1590b


git-svn-id: http://anope.svn.sourceforge.net/svnroot/anope/trunk@1 5417fbe8-f217-4b02-8779-1006273d7864

9 files changed, 1673 insertions, 0 deletions

diff --git a/docs/BUGS b/docs/BUGS
new file mode 100644
index 000000000..cbf2d5bad
--- /dev/null
+++ b/docs/BUGS
@@ -0,0 +1,17 @@
+Reported Bugs from Mantis: http://www.anope.org/bug
+===================================================
+
+.- Strange Segfault on expiring nicknames. Almost arbitrary, very hard
+   to reproduce.
+
+.- Clone detection can give false warnings if a user connects and then 
+   signs off several times in rapid succession. Clone detection also 
+   goes off wrongly if a server links and has a number of clients from 
+   the same hostname.
+
+.- If there is absolutely no activity on your network, Services may delay
+   timed events (nick kills, database saving, etc.) until the next message
+   comes in from Services' uplink server.
+
+.- Modules will not work on OpenBSD machines, due to limitations on libdl.
+
diff --git a/docs/COPYING b/docs/COPYING
new file mode 100644
index 000000000..a43ea2126
--- /dev/null
+++ b/docs/COPYING
@@ -0,0 +1,339 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                          675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	Appendix: How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) 19yy  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19yy name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/docs/DEFCON b/docs/DEFCON
new file mode 100644
index 000000000..1b7b169de
--- /dev/null
+++ b/docs/DEFCON
@@ -0,0 +1,111 @@
+Anope DefCon 
+------------
+
+Introduction:
+
+    Anope 1.6 onwards supports a unique protection mechanism based on the
+    military "Defense Readiness Condition" (DefCon) system. It is based on 
+    5 levels of defense readiness defined as:
+
+    DEFCON5 Normal peacetime readiness
+    DEFCON4 Increased intelligence and security readiness
+    DEFCON3 Increase in force readiness
+    DEFCON2 Further increase in force readiness
+    DEFCON1 Maximum force readiness.
+
+    These are configurable levels that mandates what actions Anope should
+    take in case of emergency and change in readiness status.
+
+    It is used to prevent abuse to both Services, and the ircd on which they 
+    are running. Also to protect the users, primarily in the event of Clones
+    and/or FloodBOT attacks. 
+
+Installation:
+
+    The DefCon system is part of Anope's core,
+
+    The DefCon system has to be configured on your services.conf file to
+    be enabled. All directives are optional unless they depend on what
+    options you enable for each level. Look for the "DefCon configuration"
+    section on your services.conf file for more information.
+
+    Make sure you restart Anope after changing the DefCon configuration
+    directives.
+
+Configuration:
+
+    Pre-defined DefCon actions:
+
+    No new channel registrations                       1 
+    No New Nick Registrations                          2 
+    No MLOCK changes                                   4 
+    Force Chan Mode                                    8 
+    Use Reduced Session Limit                         16 
+    KILL any new clients trying to connect            32 
+    Services will ignore everyone but opers           64 
+    Services will silently ignore everyone but opers 128 
+    AKILL all new clients trying to connect          256 
+    No new memos sent to block memoserv attacks      512
+
+    These are the values used to determine each defcon setting, are set via: 
+
+    DefCon1 XX 
+    DefCon2 XX 
+    DefCon3 XX 
+    DefCon4 XX 
+
+    To set the desired value, you simply add the value of the numbers together 
+    and place that as your DefCon# setting. For instance:
+
+    Say you wish to set: 
+
+    No Channel Registrations, No Nickname Registrations and Services Ignoring 
+    everyone except for Operators. You would do this by: 
+
+    1 + 2 + 128 (Each value listed above is added together) 
+    Giving: 131 
+
+    You would then place this as which ever Defcon setting you want: 
+    
+    DefCon1 131 
+
+    The recommended default values are safe to use on any network.
+
+Usage:
+
+    Anope starts up in DEFCON5 (normal readiness). To change the Defcon level 
+    in action use: 
+    
+    /msg OperServ DEFCON 1|2|3|4|5 
+
+Example:
+
+    Place the network on DEFCON4:
+
+    /msg OperServ DEFCON 4
+
+    *** Global -- from OperServ: dengel Changed the DEFCON level to 4
+
+    -OperServ- Services are now at DEFCON 4
+    -OperServ- * No new channel registrations
+    -OperServ- * No new nick registrations
+    -OperServ- * No MLOCK changes
+    -OperServ- * Use the reduced session limit of 5
+
+    -Global- The Defcon Level is now at Level: 4
+
+    Restore normal readiness:
+
+    /msg OperServ DEFCON 5
+
+    *** Global -- from OperServ: dengel Changed the DEFCON level to 5
+
+    -OperServ- Services are now at DEFCON 5
+
+    -Global- Services are now back to normal, sorry for any inconvenience
+
+Support:
+
+    You might get DefCon support by posting on our online forum, or maybe on 
+    our #anope channel at /server irc.anope.org.
+
diff --git a/docs/FAQ b/docs/FAQ
new file mode 100644
index 000000000..014d3a34d
--- /dev/null
+++ b/docs/FAQ
@@ -0,0 +1,423 @@
+           Frequently Asked Questions (FAQ) concerning Anope
+           =================================================
+
+Index:
+
+ 1. What is Anope?
+
+ 2. Where can I find Anope?
+
+ 3. Does Anope run under Windows?
+
+ 4. Can I send you questions without reading the FAQ, INSTALL or 
+    README files?
+
+ 5. When I run "make", I get an error message like "missing separator",
+   "Unassociated shell command", "Unexpected end of line seen", etc.
+
+ 6. I get an error like "Makefile.inc not found".
+
+ 7. I typed "./services" at the command line, but nothing happened!
+
+ 8. I need support for the XYZ protocol.
+
+ 9. Whenever I start Anope, I get a message on my IRC server saying
+    "connection refused" or something similar, and Anope gives an error
+    message from the server saying "Closing Link: ...".
+
+10. My IRC server is giving me messages like "Connection to
+    services.whatever.net[127.0.0.1] activated" and then "Access denied --
+    no N line".  Why?
+
+11. When I say "/connect services.*", it doesn't work!
+
+12. Anope complains in the logfile about being unable to load the
+    default language.
+
+13. Anope always dies after about five minutes, saying "FATAL ERROR!
+    Can't back up nick.db".
+
+14. Anope starts up okay, but if I try to register a nickname, it comes
+    back with "Sorry, registration failed."
+
+15. Anope crashed with a segmentation fault.
+
+16. Anope's channel mode setting doesn't work.  I can't set modes with
+    OperServ, and every time ChanServ tries to set a mode, my server
+    reverses the change.
+
+17. Using the OperServ JUPE command results in server messages like
+    "Server juped.server introduced by non-hub server services.my.net".
+
+18. I can't use the ADMIN command to add Services admins--it tells me
+    "Permission denied."
+
+19. When I add an AKILL, the users matching it don't get killed.
+
+20. Anope reports (via /stats u or /msg OperServ STATS) a different
+    number of users online than I get from doing /lusers.
+
+21. Anope ignored the SET SUCCESSOR setting and deleted a channel when
+    the founder expired.
+
+22. Trying to use OperServ gives me "Access denied", but my nick is in the
+    ServicesRoot directive and is registered, and I've identified for my
+    nick.
+
+23. Anope spricht kein Deutsch!, etc.  (Anope doesn't speak my
+    language!)
+
+24. I selected a language other than English, but sometimes Anope sends
+    responses in English instead.
+
+25. I've found a bug that's not mentioned here or in the
+    BUGS files.  What should I do?
+
+26. Your Services program doesn't do XYZ like DALnet Services.  What's
+    wrong?
+
+27. I've got a great new idea for Anope.  Do you want it?
+
+28. Examples of features I have been asked about and why we won't add (or
+      haven't yet added) them--so don't ask us about them.
+      
+29. How do I add bots to BotServ?
+
+30. When I used the OperServ RAW command, Anope and/or my network
+    crashed, or did weird things! Please fix this bug!
+
+31. I would like to have the list of the differents RAW on operserv
+
+32. I can't get /OS UMODES and /OS SVSNICK do not work!
+
+33. What is a Super-Admin? How does it work? Why might it not work?
+
+---------------------------------------------------------------------------
+
+1. What is Anope?
+
+	Anope is a set of services for IRC networks.  See the README
+	file for more information. And in case you were wondering, 
+	Anope is Epona spelt backwards :)
+
+
+2. Where can I find Anope?
+
+	The latest version can always be found at the official Anope
+	distribution site:
+
+	http://www.anope.org/
+
+	New version announcements can also be found at http://anope.zero.org/
+	in the Announcement section.
+
+
+3. Does Anope run under Windows?
+
+	Well... not officialy. Bu there is a cygwin based patch that makes
+	Anope work on Windows. Note, however, that some features might not
+	work, and you should take that into consideration when answering
+	the questions of ./configure (i.e. MySQL, Modules). 
+
+	You can obtain a pre-build copy of Anope for Windoes from 
+	http://www.wircds.net/ although we have "blessed" that port,
+	we do not provide support for it. If you can't get it work,
+	go to wIRCds.net forum.
+
+	If you feel capable of taking ownership of an official windows
+	port, and to keep it current, please let the current Development 
+	team know.
+
+
+4. Can I send you questions without reading the FAQ, INSTALL or README 
+   files?
+
+	No. If you don't read those files, your messages will most probably
+	be ignored. We don't mean to be rude, but if we took the time
+	to write down some documentation, we'd expect you to take some
+	time to read it.
+
+
+5. When I run "make", I get an error message like "missing separator",
+   "Unassociated shell command", "Unexpected end of line seen", etc.
+
+	Your make program isn't compatible with the Makefile for Anope.
+	The Makefile was designed to work with GNU make, and as such may
+	not work on other systems' "make" programs.  If you get an error
+	from "make", obtain GNU make from ftp://prep.ai.mit.edu/pub/gnu/
+	(or wherever you prefer) and use it instead of your system's
+	default "make".  Note that GNU make may already be installed on
+	your system; try using the command "gmake" instead of "make".
+
+	The make programs bundled with SunOS/Solaris and FreeBSD have been
+	reported not to work; you will need to use GNU make on these
+	systems.
+
+6. I get an error like "Makefile.inc not found".
+
+	You forgot to run the configure script first.  See the INSTALL file
+	for compilation instructions.
+
+
+7. I typed "./services" at the command line, but nothing happened!
+
+	Anope puts itself in the background when it starts, so you get
+	your shell prompt right back.  Meanwhile, Anope will continue
+	setting up, then connect to the IRC server specified in
+	services.conf (or on the command line).  If it doesn't connect, you
+	probably specified the wrong server type when running the configure
+	script.  (Also make sure that you are actually running one of the
+	supported servers.  There are a gazillion different variations on
+	the basic IRC protocol out there, and I have neither the time nor
+	the desire to add support for them.)
+
+	The recommended server, under which Epona (the original code base
+	used by Anope) was developed, is Bahamut. DreamForge 4.6.7 will also 
+	work fine, but it's a bit obsolete nowadays. Derivatives of Bahamut
+	and DreamForge may also work, if they don't change the server<->server 
+	protocol too much; contact their authors for more information.
+	Most people, though, are running Anope with UnrealIRCd, UltimateIRCd
+	or Bahamut.
+
+	As always, you can check the log file (services.log by default) for
+	error messages.
+
+
+8. I need support for the XYZ protocol.
+
+	Hang in there! We are working on making Anope protocol independent.
+	It should show up sometime soon... more details to follow.
+
+
+9. Whenever I start Anope, I get a message on my IRC server saying
+    "connection refused" or something similar, and Anope gives an error
+    message from the server saying "Closing Link: ...".
+
+	See seection 3 of the INSTALL file.
+
+
+10. My IRC server is giving me messages like "Connection to
+    services.whatever.net[127.0.0.1] activated" and then "Access denied --
+    no N line".  Why?
+
+	This is typically caused by including a port number in the C:line
+	for services, which tells your server to try to autoconnect to it
+	(depending on the class (Y:line) settings).  This is not what you
+	want, because Anope will connect to the server itself, but does
+	not listen for servers to connect to it.  The solution is to remove
+	the port number from the C:line.
+
+
+11. When I say "/connect services.*", it doesn't work!
+
+	Of course not.  RTFM (Read The Fine Manual), and see the previous
+	answer.
+
+
+12. Anope complains in the logfile about being unable to load the
+    default language.
+
+	You forgot to run "make install".
+
+13. Anope always dies after about five minutes, saying "FATAL ERROR!
+    Can't back up nick.db".
+
+	Make sure that the user Anope runs as has write access to the
+	data directory, and that the data directory actually exists (the
+	latter shouldn't be a problem if you ran the configure script).
+	This means Anope needs write and execute permission on the data
+	directory itself and execute permission on every parent directory
+	of the data directory.
+
+
+14. Anope starts up okay, but if I try to register a nickname, it comes
+    back with "Sorry, registration failed."
+
+	Make sure you've selected the correct IRC server type in the
+	configure script; see question 9 for details.
+
+
+15. Anope crashed with a segmentation fault.
+
+	See if you can reproduce this by doing a certain sequence of
+	things.  If so, please report it to us (see part 6 of README file).  If
+	not, you're probably out of luck; if you like, you can report it to
+	us anyway, but chances are it won't get fixed if we don't have
+	instructions on reproducing it.  If you do have such a problem, you
+	may find the crontab utility useful for dealing with it.
+
+	Also, see the DumpCore directive in the configuration file. It allows
+	Anope to dump its core whenever it's segfaulting, usually calling it
+	core and placing it into Anope's main directory.
+	Open up gdb by issuing the following command at your shell:
+	   gdb services core
+	(of course replacing 'core' with the name of the core if different)
+	and type 'bt' at the gdb prompt. After that, send us the output you
+	got and keep the core file in a safe place, in case we need it to
+	dig deeper into the problem.
+
+16. Anope's channel mode setting doesn't work.  I can't set modes with
+    OperServ, and every time ChanServ tries to set a mode, my server
+    reverses the change.
+
+	Make sure EVERY servers on your network has a U: line for Services in
+	ircd.conf, for example:
+
+	U:services.whatever.net:*:*
+
+
+17. Using the OperServ JUPE command results in server messages like
+    "Server juped.server introduced by non-hub server services.my.net".
+
+	Services' uplink must have an H: line for Services in the
+	ircd.conf file, which looks something like:
+
+	H:*::services.whatever.net
+
+
+18. I can't use the ADMIN command to add Services admins--it tells me
+    "Permission denied."
+
+	Did you define yourself as the Services root?  You need to insert
+	your nickname in the ServicesRoot directive in services.conf.
+
+
+19. When I add an AKILL, the users matching it don't get killed.
+
+	Use the AkillOnAdd configuration directive.
+
+
+20. Anope reports (via /stats u or /msg OperServ STATS) a different
+    number of users online than I get from doing /lusers.
+
+	Anope doesn't count its own pseudo-clients (NickServ, ChanServ,
+	etc.) in its user count.
+
+
+21. Anope ignored the SET SUCCESSOR setting and deleted a channel when
+    the founder expired.
+
+	Normally, this is because the successor had too many channels
+	registered; in this case, you will see an entry in the log file
+	like the following:
+
+	[date] Successor (SuccessorNick) of channel #somechannel owns too
+	       many channels, deleting channel #somechannel
+
+	If you don't get a message like this or you can verify that the
+	successor wasn't running into the channel limit, please report it
+	using the bug-reporting procedure below (see section 6 of the 
+	README file).
+
+
+22. Trying to use OperServ gives me "Access denied", but my nick is in the
+    ServicesRoot directive and is registered, and I've identified for my
+    nick.
+
+	You need to be opered (i.e. user mode +o) to access OperServ.
+
+
+23. Anope spricht kein Deutsch!, etc.  (Anope doesn't speak my
+    language!)
+
+	See section 5 of the README file.
+
+
+24. I selected a language other than English, but sometimes Anope sends
+     responses in English instead.
+
+	Some language files are not complete--in other words, they don't
+	have a translation of every message Anope uses, but only some of
+	them.  In this case, the missing messages will be displayed in
+	English.  You can either wait for the primary translator to provide
+	us with a translation, or do the translation yourself and send us
+	the messages translated into your language.
+
+
+25. I've found a bug that's not mentioned here or in the README or
+    BUGS files.  What should I do?
+
+	See section 6 of the README file.
+
+
+26. Your Services program doesn't do XYZ like DALnet (or other) Services.  
+    What's wrong?
+
+	Nothing is wrong, except your expectations.  Anope is a
+	completely different program from that used on DALnet; they are
+	similar in concept only.
+
+
+27. I've got a great new idea for Services.  Do you want it?
+
+	We are always interested in hearing new ideas.  HOWEVER, do not
+	expect your proposal to be in the next Anope release for sure.
+	As a rule, we usually don't add anything that can be equivalently
+	done by other means, or that we consider totally useless; see below
+	for examples of things we don't plan to add.
+
+	Our general intent is for Anope to provide as much functionality
+	as possible--while staying as lean as possible.  So features which 
+	are arguably beneficial will tend to be added, while features of
+	limited or no benefit or which can be equally provided by something
+	else already in use will tend to be passed over.
+
+	If you'd like to give us your idea, you can go to our website at
+	http://www.anope.org/ and add it as a Feature Request on our Bug
+	Tracking System. Or, if unsure, you can discuss it on our online
+