This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
help:technical [2007/02/13 21:20] – created rubin | help:technical [2017/05/23 21:08] (current) – rubin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | ssh into your server. | + | * [[help: |
- | Then run: | + | * [[help:technical:loc|Login-on-Connect Extension]]: |
- | svn co https:// | + | |
- | The system will begin to download the latest version of the nefarious ircu. | + | * [[help: |
- | Before we continue, we'd like to make sure you have the packages needed for a successful install. | + | * [[help: |
- | So be sure you have the packages below installed on your box: | + | |
- | | + | |
- | libssl-dev (for enabling ssl -- openssl-devel on redhat) | + | |
- | autoconf (to avoid errors when running make) | + | |
- | automake | + | |
- | The named packages above can be fetched (on a Debian based system) with apt-get: | ||
- | |||
- | sudo apt-get install open-ssl libssl-dev autoconf automake | ||
- | |||
- | Note: The names of the packages above may vary, depending on your distribution. | ||
- | |||
- | With that said, we now move on to getting the server up and running. | ||
- | |||
- | cd nefarious | ||
- | |||
- | For your own convenience, | ||
- | |||
- | ./configure --libdir=/ | ||
- | |||
- | Once that is done, run: | ||
- | |||
- | make | ||
- | |||
- | Then: | ||
- | |||
- | make install | ||
- | |||
- | If everything runs smoothly you should now have an ircd directory: | ||
- | |||
- | cd / | ||
- | |||
- | Then fetch the ircd.conf to the ircd directory: | ||
- | |||
- | wget -O ircd.conf http:// | ||
- | |||
- | You'll have to edit the configuration file a bit (for simplicity, nano is used in this example): | ||
- | |||
- | nano ircd.conf | ||
- | |||
- | Change the M:line to look similar to this: | ||
- | |||
- | M: | ||
- | |||
- | Where YourNumeric would be changed to a number we give you. | ||
- | |||
- | Next change the A:line: | ||
- | |||
- | A: | ||
- | |||
- | You might also want to give yourself an O:line, otherwise you can't oper up. Now save the file. | ||
- | |||
- | You are now ready to start your IRC server, run: | ||
- | |||
- | ./ircd | ||
- | |||
- | That will start the ircd. Test it by connecting to your server. | ||
- | Installing the cronjobs needed | ||
- | Cron is the system scheduled jobs manager. We generally run 3 jobs to help maintain the ircd. To edit the cron list, login with the account on which you want the scheduled jobs to run under, and run: | ||
- | crontab -e | ||
- | |||
- | The syntax of the file is as follows: | ||
- | < | ||
- | # Min Hour Day | ||
- | */5 | ||
- | </ | ||
- | read the unix manual to crontab for more information. | ||
- | |||
- | === Please install the following cronjobs: === | ||
- | |||
- | == linesync == | ||
- | linesync updates your server 2x a day with the latest k: lines, features, and server connection lines. It is required. You should receive it from us when your testlink is approved. | ||
- | |||
- | 0 */12 * * * / | ||
- | |||
- | == checkircd.sh == | ||
- | This gem checks if the irc server is running, and if it isnt, starts it up. This will keep the ircd up after reboots, or in the case of a crash. Create the file using a text editor, pasting this code in: | ||
- | < | ||
- | #!/bin/sh | ||
- | # don't start the server if it is already running | ||
- | procs=`ps x` | ||
- | if echo " | ||
- | exit | ||
- | fi | ||
- | cd / | ||
- | ./ircd | ||
- | </ | ||
- | (be careful to use the right kind of `` ticks!) | ||
- | |||
- | chmod a+x checkircd.sh to make it executable | ||
- | < | ||
- | */5 * * * * / | ||
- | </ | ||
- | == syncheck == | ||
- | |||
- | syncheck is our anti-ddos attack tool, you should have received from us on successful testlink. It requires iptables, and thus root access: Put it in /root (or wherever you want) and as root run: | ||
- | |||
- | crontab -e | ||
- | |||
- | And install the following cronjob: | ||
- | < | ||
- | */5 * * * * sh / | ||
- | </ | ||
- | With these cronjobs installed, you are now ready to link your server to the network. |