| 1 |
Hybrid INSTALL Document |
| 2 |
|
| 3 |
$Id$ |
| 4 |
|
| 5 |
Copyright (c) 1997-2013 IRCD-Hybrid Development Team |
| 6 |
|
| 7 |
---------------------------------------------------------------------- |
| 8 |
|
| 9 |
+------------------------------------------------------------------------+ |
| 10 |
| Note for those who don't bother reading docs: | |
| 11 |
| | |
| 12 |
| Reading INSTALL is now a must, as the old DPATH is now specified when | |
| 13 |
| configure is run. | |
| 14 |
| | |
| 15 |
| - You now need to ./configure --prefix="/path/to/install/it" as a | |
| 16 |
| minimum. Try ./configure --help or read this file for more info on | |
| 17 |
| the possible options you can pass to configure. | |
| 18 |
| | |
| 19 |
| - Important: The old config format WILL NOT WORK. Please see point 6! | |
| 20 |
+------------------------------------------------------------------------+ |
| 21 |
|
| 22 |
***** EFNET NOTE ***** |
| 23 |
You should use the example.efnet.conf instead of example.conf. |
| 24 |
********************** |
| 25 |
|
| 26 |
---------------------------------------------------------------------- |
| 27 |
|
| 28 |
HOW TO BUILD |
| 29 |
|
| 30 |
As of hybrid-4, the distribution uses GNU autoconf instead of the old |
| 31 |
Config script. You must run ./configure before you can (sanely) build |
| 32 |
ircd-hybrid. |
| 33 |
|
| 34 |
1. Read the NEWS file to find out about the exciting new features in |
| 35 |
this version. Other good reads are BUGS, doc/example.conf, and |
| 36 |
README. |
| 37 |
|
| 38 |
2. Run the configure script. It will create config.h and the |
| 39 |
Makefiles to match your system. The paths are now handled |
| 40 |
with the --prefix option to configure. |
| 41 |
/usr/local/ircd is the default if no prefix is specified. |
| 42 |
|
| 43 |
./configure --prefix=/usr/local/ircd |
| 44 |
|
| 45 |
The script will determine whichever of the following is best for |
| 46 |
your system, but you may (unsupported) force their usage with |
| 47 |
undefined results: |
| 48 |
|
| 49 |
* --enable-kqueue - Use the superior kqueue(2) system call as |
| 50 |
opposed to the default poll(2). This is currently only available |
| 51 |
on FreeBSD 4.1 or higher. |
| 52 |
|
| 53 |
* --enable-devpoll - Enable the superior /dev/poll support on |
| 54 |
Solaris. Linux /dev/poll is broken and will not work with this |
| 55 |
option. |
| 56 |
|
| 57 |
* --enable-epoll - Enables epoll(4) Signal I/O system. This is |
| 58 |
currently only available on 2.5.44 Linux kernel versions or |
| 59 |
later. |
| 60 |
|
| 61 |
* --enable-poll - Use POSIX poll(2). |
| 62 |
|
| 63 |
* --enable-select - Use POSIX select(2). |
| 64 |
|
| 65 |
Incidentally, the order of listing above is the order of auto- |
| 66 |
detection in configure. So if you do have kqueue but wish to |
| 67 |
enable select(2) instead (bad idea), you must use --enable-select. |
| 68 |
|
| 69 |
* --enable-openssl - Enable the openssl dependent crypto functions. |
| 70 |
Required for the SSL Challenge controlled OPER feature, compressed |
| 71 |
and/or SSL/TLS server links, as well as SSL/TLS client connections. |
| 72 |
|
| 73 |
On systems where the configure script can automatically detect |
| 74 |
OpenSSL, this option is not necessary. If configure cannot find |
| 75 |
OpenSSL, you must specify a path with this option |
| 76 |
(--enable-openssl=/path/to/openssl) |
| 77 |
|
| 78 |
|
| 79 |
These are optional or have default values that may be overridden: |
| 80 |
|
| 81 |
* --enable-assert - Enable use of numerous debugging checks. This |
| 82 |
should not be used on any production servers for maximum speed |
| 83 |
so as to prevent cores from things that shouldn't normally happen. |
| 84 |
|
| 85 |
* --enable-halfops - Enable halfops (%, mode +h) usage. Halfops |
| 86 |
are similar to plain ops, but can't kick/deop plain ops. Halfops |
| 87 |
may or may not kick/deop other halfops depending on if (+p) is |
| 88 |
set. Halfops may not set (+/-p). |
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
3. Run 'make'; this should build the ircd. |
| 93 |
|
| 94 |
4. Run 'make install'; this will install the server, modules, and tools |
| 95 |
in the path with the prefix specified when configure was ran. |
| 96 |
|
| 97 |
5. If you wish to install the contrib modules, run 'make install' in the |
| 98 |
contrib/ folder to compile and install the modules and help pages. |
| 99 |
|
| 100 |
6. If you are upgrading from Hybrid 5 or Hybrid 6, the config files |
| 101 |
have changed drastically. |
| 102 |
|
| 103 |
By default, the kline file is named kline.conf, the dline file is |
| 104 |
named dline.conf, and the xline file is called xline.conf. |
| 105 |
|
| 106 |
The nick resv file is named nresv.conf, channel resv file is named |
| 107 |
cresv.conf. |
| 108 |
|
| 109 |
---------------------------------------------------------------------- |
| 110 |
|
| 111 |
HOW TO GET HELP |
| 112 |
|
| 113 |
- Send Check or Money Order to... just kidding! You're on your own for |
| 114 |
support. Try asking other ircd-hybrid admins on EFnet if you can't |
| 115 |
fix it yourself. If you do fix anything, however, please send context |
| 116 |
or unified diffs to bugs@ircd-hybrid.org so the fixes can be |
| 117 |
incorporated into the next release of ircd-hybrid. If hybrid crashes |
| 118 |
on you, PLEASE contact bugs@ircd-hybrid.org ASAP with a backtrace of |
| 119 |
the core. The Hybrid team can't fix bugs if no one tells us about them! |
| 120 |
|
| 121 |
- https://lists.ircd-hybrid.org/mailman/listinfo/hybrid |
| 122 |
Here you can subscribe to a mailing list for general discussion of Hybrid. |
| 123 |
|
| 124 |
---------------------------------------------------------------------- |
| 125 |
|
| 126 |
NOTES |
| 127 |
|
| 128 |
The best way to get a backtrace of the core is to follow this sequence of |
| 129 |
instructions: |
| 130 |
|
| 131 |
1. Change to the directory containing the core file |
| 132 |
|
| 133 |
2. Run gdb on the binary and the core file. With an unmodified ircd-hybrid |
| 134 |
installation, an example command line is below (in the /usr/local/ircd |
| 135 |
directory) |
| 136 |
|
| 137 |
$ gdb bin/ircd ircd.core |
| 138 |
|
| 139 |
|
| 140 |
3. At the "(gdb)" prompt, enter the command "bt full" |
| 141 |
|
| 142 |
4. Save the output of the backtrace command and send it to |
| 143 |
bugs@ircd-hybrid.org. |
| 144 |
|
| 145 |
5. Be sure to save the ircd binary, the modules, and the core file in a |
| 146 |
safe place in case the developers need to look deeper than a backtrace |
| 147 |
provides. |
