IRCD Help | UnrealIRCD | Services | NeoStats | EggDrop | psyBNC | Modules

How to setup crontab for UnrealIRCD

2013-08-08T06:48:00.000-07:00

ircd.cron.in
0,10,20,30,40,50 * * * * @IRCDDIR@/ircdcron/ircdchk >/dev/null 2>&1

ircdchk.in
#!/bin/sh
#
# UnrealIRCD Crontab v2.1
# $Id$
#
# This is a script suitable for use in a crontab. It checks to make sure
# your ircd is running. YOU NEED A SEPARATE CRON JOB FOR EACH IRCD. If your
# ircd isn't found, it'll try to start it back up.
#
# You'll need to edit this script for your ircd.
#
# To check for your ircd every 10 minutes, put the following line in your
# crontab:
# 0,10,20,30,40,50 * * * * /home/mydir/ircdchk
# And if you don't want to get email from crontab when it checks you ircd,
# put the following in your crontab:
# 0,10,20,30,40,50 * * * * /home/mydir/ircdchk >/dev/null 2>&1
#
# change this to the mail address to mail output to:
# MAIL=me
# These values shouldn't need to be changed
# The path to the ircd binary
ircdexe="@BINDIR@"
# The path to the ircd pid file
ircdname="@IRCDDIR@/ircd.pid"
########## don't change anything below here ##########
if test -r $ircdname; then
# there is a pid file -- is it current?
ircdpid=`cat $ircdname`
if `kill -CHLD $ircdpid >/dev/null 2>&1`; then
    # it's still going
    # back out quietly
    exit 0
fi
echo "UnrealIRCd Crontab notice:"
echo ""
echo "Stale $ircdname file (erasing it)"
rm -f $ircdname
fi
echo ""
echo "Couldn't find the ircd running. Reloading it..."
echo ""
$ircdexe

How to setup crontab for psyBNC

2013-08-08T06:43:00.000-07:00

First thing to do is you must edit psbncchk file in your psyBNC folder.
$ nano psybncchk
Search for this line:
PSYBNCPATH=/home/zemra/psybnc
Change the path into your psyBNC path, look at this example:
PSYBNCPATH=/home/zemra/psybnc
Save the file and exit the editor.
Change the default editor by using this command:
$ export EDITOR=nano

Next step is editing the crontab file:
$ crontab -e
Insert this line to the file:
0,10,20,30,40,50 * * * * /home/zemra/psybnc/psybncchk >/dev/null 2>&1
Remember, change the path to your psybnc path.
This crontab command means it will run the psybncchk file every 10 minutes.

How to setup Crontab for an Eggdrop?

2013-08-08T06:18:00.001-07:00

PART 1:
"botchk" setup
locate the botchk file in the bots main dir.
type ->     pico botchk
    You need to edit 4 things in the "botchk"
# change this to the directory you run your bot from:
botdir="/usr/home/user/botdir/"

# change this to the name of your bot's script in that directory:
botscript="./eggdrop eggdrop.conf"

# change this to the nickname of your bot (capitalization COUNTS)
botname="BotNick"

# change this to the name of your bot's userfile (capitalization COUNTS)
userfile="bot.user"
type ->     ctrl+o     Save the file
type ->     ctrl+x     exit pico

PART 2:
Setting up the crontab file
type ->     pico crones     this will be your crontab file
type ->     0,10,20,30,40,50     * * * *     /home/user/botdir/botchk     >/dev/null 2>&1
-     ^--(1)     ^--(2)     ^--(3)     ^--(4)
-     1. time in (minutes) it will check to see if the bot is running
2. tells it to run every hour/day of month/month/year
3. full system path to the location of your botchk file
4. tells the system not to send you mail everytime crontab loads the bot or checks to see if the bot is running (this is a good idea because some sys admins might get upset with all of the emails)
type ->     ctrl+o     Save the file
type ->     ctrl+x     exit pico
type ->     crontab crones     This will load the file "crones" into your crontab. You can check your crontab by typing "crontab -l"

How to install IRC Defender

2013-04-26T20:41:00.003-07:00

IRC Defender is a piece of IRC software (a bot) that is used to help ban proxies and keep your server secure. When a user connects via a proxy they are scanned by defender and a ban is placed on them if they are found to be using a proxy. Defender is one of the easiest IRC programs to install and set up. To install IRC Defender follow these steps:

Log into your server using SSH
wget –no-check-certificate https://www.hostchaos.com/library/IRC/defender-1.5.1.tar.bz2
tar xvjf defender-1.5.1.tar.bz2

1) Firstly log into your server using WinSCP.
2) Enter your folder called Defender by double clicking on it.
3) You are presented with a list of files and folders, look for a file called defender.conf.example and rename it to defender.conf .
4) Open it and begin editting as necessary following the instructions throughout the config.
5) Save and close it.
During the editing of the defender.conf you will have had to set up a link block, you’ll need to add a link block to the unrealircd.conf and a U:Line. To do this you’ll need to do the following:
1) Open unrealircd.conf .
2) Scroll down to the section in the configuration where link blocks are added and create a link block for defender.
link              IRC.Zemra.Org
{
username *;
hostname 72.73.74.75;
bind-ip *;
port 3366;
hub             *;
password-connect “IRCD”;
password-receive “IRCD”;
class           servers;
options {
};
};
3) In unrealircd.conf you also need to create a listen block. If you scroll to the section in your unrealircd.conf with a list of listen blocks already there copy and paste one directly underneath the list and change the port to 7000 so it is listening on that port for defender to connect.
Example: Listen 72.73.74.75:3366
4) Last bit you need to add to the unrealircd.conf is the U:Line, scroll to the section of the unrealircd.conf where your U:Lines are and add a U:Line for the defender server. Here’s an example:
ulines {
ircdefenders.domain.com;
};
5) Save and close the unrealircd.conf.
6) On your server type /rehash .
Now you need to run defender.
1) Log into your server using SSH and type:.

cd defender
perl defender.pl

How to install flashpolicyd

2013-04-26T09:56:00.001-07:00

How to install flashpolicyd

wget http://www.lightirc.com/release/flashpolicyd.zip
unzip flashpolicyd.zip
cd flashpolicyd
chmod a+x flashpolicyd.rb
whereis ruby ruby: /usr/local/bin/ruby /usr/local/man/man1/ruby.1.gz
edit flashpolicyd.rb (change the first line to /usr/local/bin/ruby)
edit check_flashpolicyd.rb (change the first line to /usr/local/bin/ruby)
./flashpolicyd.rb --xml flashpolicy.xml --logfile flashpolicyd.log --port 8002
tail flashpolicyd.log - Verify that flashpolicyd is running

Installing Ruby on FreeBSD

2013-03-25T00:52:00.001-07:00

The object-oriented programming language is available as a port on FreeBSD. Ruby combines syntax inspired by Perl with Smalltalk-like features and is influenced by Eiffel and Lisp as well. With Ruby you can make use of multiple programming paradigms, including functional, object oriented, imperative and reflective. The automatic memory management and a dynamic type system are one of the main key factors to use Ruby.

Root access is required to edit the following files and to execute commands. Log in as root (su) or simply prepend sudo to all commands that require root privileges.

Install Ruby 1.8

With the following commands you will install Ruby 1.8 from the ports directory:

cd /usr/ports/lang/ruby18/
make install clean; rehash

At this point Ruby 1.8 is installed. If you want to use a newer version, RVM can help you. This tutorial also explains how to install the RVM manager.

Install Curl

Install Curl for later use.

cd /usr/ports/ftp/curl
make install clean; rehash

Install Bash

Bash is needed to use Ruby properly.

cd /usr/ports/shells/bash
make install clean; rehash

Install Git

The following commands will install Git:

cd /usr/ports/devel/git
make install clean; rehash

Create a user

Add a new user for your Ruby environment.

adduser

Username: rvm
Full name: Ruby Version Manager
Uid (Leave empty for default): 
Login group [rvm]: 
Login group is rvm. Invite rvm into other groups? []: 
Login class [default]: 
Shell (sh csh tcsh bash rbash nologin) [sh]: bash
Home directory [/home/rvm]: 
Home directory permissions (Leave empty for default): 
Use password-based authentication? [yes]: no
Lock out the account after creation? [no]: no
Username   : rvm
Password   : 
Full Name  : Ruby Version Manager
Uid        : 1001
Class      : 
Groups     : rvm 
Home       : /home/rvm
Home Mode  : 
Shell      : /usr/local/bin/bash
Locked     : no
OK? (yes/no): yes
adduser: INFO: Successfully added (rvm) to the user database.

Log in as user

su rvm

Install RVM

The following command will install the RVM manager:

bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer )

Downloading RVM from wayneeseguin branch stable
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  796k  100  796k    0     0   941k      0 --:--:-- --:--:-- --:--:-- 4490k

Installing RVM to /home/rvm/.rvm/
installing - /home/rvm/.rvm/man/man1/rvm.1 -
installing - /home/rvm/.rvm/man/man1/rvm.1.gz -

# RVM:  Shell scripts enabling management of multiple ruby environments.
# RTFM: https://rvm.beginrescueend.com/
# HELP: http://webchat.freenode.net/?channels=rvm (#rvm on irc.freenode.net)
# Screencast: http://screencasts.org/episodes/how-to-use-rvm

# In case of any issues read output of 'rvm requirements' and/or 'rvm notes'

Installation of RVM in /home/rvm/.rvm/ is almost complete:

  * To start using RVM you need to run `source /home/rvm/.bashrc`
    in all your open shell windows, in rare cases you need to reopen all shell windows.

# rvm,
#
#   Thank you for using RVM!
#   I sincerely hope that RVM helps to make your life easier and more enjoyable!!!
#
# ~Wayne

Load RVM at login

Type these commands into the console to start RVM at login:

echo '[[ -s "$HOME/.rvm/scripts/rvm" ]] && . "$HOME/.rvm/scripts/rvm" # Load RVM function' >> ~/.bash_profile
echo '[[ -s "$HOME/.rvm/scripts/rvm" ]] && . "$HOME/.rvm/scripts/rvm" # Load RVM function' >> ~/.bashrc

Reload Bash profile

Reload your Bash profile so that the previous changes can take effect.

source ~/.bash_profile

Check that all is OK

Receiving an other response than rvm is a function means that RVM is not loaded.

type rvm | head -1

rvm is a function

List available Ruby versions

Now, you can list the available Ruby versions with the following command:

rvm list known

Install Ruby

Install your favorite Ruby version.

rvm install 1.9.3-head

Set the default Ruby version

Set the just installed Ruby version as default.

rvm use 1.9.3-head --default

Check your installed Ruby version

Check your Ruby version with this command:

ruby -v

How to Upgrade Anope Services

2013-02-21T08:48:00.000-08:00

Upgrading Anope Services

Upgrading Anope Services
------------------------

1) Log into SSH.
2) Type wget https://www.hostchaos.com/library/IRC/anope-1.8.7.tar.gz
tar -zxvf anope-1.8.7.tar.gz
cd ~
cd anope-1.8.7
./Config
What directory - Enter
Data files - Enter
Data files owned - Enter
Default umask - 077
Check for mysql libraries - No
Once it has finished configuring, type "make"
Then "make install"

Now you have installed the latest version of Anope on your server, you now need to copy over the database files and services.conf file. Before copying over the services.conf file, read the changes.conf and add any changes to your services.conf file. If you are upgrading from a much older version (say 1.8.0 or before) it would probably be easier to create a fresh configuration file from the example.conf included in the new version you have just installed (edit example.conf as necessary, save, and rename to services.conf).

1) Log into your server with WinSCP
2) Copy over your backed up database files into the Services folder
3) Copy over your EDITED services.conf (if necessary)

Now you need to restart your services.
Restart from your IRC client by typing /msg OperServ restart
cd services
./services start

How to Upgrade UnrealIRCD

2013-02-21T01:32:00.003-08:00

How to Upgrade UnrealIRCD

The recommended way to upgrade is:
Linux:

Rename your old UnrealIRCd directory (or otherwise you’ll overwrite it in the next step)
Extract the new UnrealIRCd version and run ./Config and make
Copy your old configuration files to the new directory (unrealircd.conf, motd, rules, server.* [SSL certs], network file, etc)

Windows:

Copy all of your configuration files to a temporary location.
Run the uninstaller for any previous versions of Unreal you have installed.
Run the installer for the new version of Unreal.
Copy your old configuration files to the new folder.

Installation Instructions
Linux:

gunzip -d Unreal3.2.X.tar.gz
tar xvf Unreal3.2.X.tar
cd Unreal3.2
./Config
Answer these questions to the best of your knowledge. Generally if your not sure, the default will work just fine!
make
Now create your unrealircd.conf and other configuration files, see section 4.

Windows:

Run the Unreal installer
Now create your unrealircd.conf and other configuration files, see section 4.

NickServ

2012-01-15T03:53:00.000-08:00

HELP

NickServ allows you to "register" a nickname and
prevent others from using it. The following
commands allow for registration and maintenance of
nicknames; to use them, type /msg NickServ command.
For more information on a specific command, type
/msg NickServ HELP command.

REGISTER

Syntax: /msg NickServ REGISTER password [email]

Syntax: REGISTER password [email]

Registers your nickname in the NickServ database. Once
your nick is registered, you can use the SET and ACCESS
commands to configure your nick's settings as you like
them. Make sure you remember the password you use when
registering - you'll need it to make changes to your nick
later. (Note that case matters! ANOPE, Anope, and
anope are all different passwords!)

Guidelines on choosing passwords:

Passwords should not be easily guessable. For example,
using your real name as a password is a bad idea. Using
your nickname as a password is a much worse idea ;) and,
in fact, NickServ will not allow it. Also, short
passwords are vulnerable to trial-and-error searches, so
you should choose a password at least 5 characters long.
Finally, the space character cannot be used in passwords.

The parameter email is optional and will set the email
for your nick immediately. However, it may be required
on certain networks.
Your privacy is respected; this e-mail won't be given to
any third-party person.

This command also creates a new group for your nickname,
that will allow you to register other nicks later sharing
the same configuration, the same set of memos and the
same channel privileges. For more information on this
feature, type /msg NickServ HELP GROUP.

GROUP

Syntax: /msg NickServ GROUP target password

Syntax: GROUP target password

This command makes your nickname join the target nickname's
group. password is the password of the target nickname.

Joining a group will allow you to share your configuration,
memos, and channel privileges with all the nicknames in the
group, and much more!

A group exists as long as it is useful. This means that even
if a nick of the group is dropped, you won't lose the
shared things described above, as long as there is at
least one nick remaining in the group.

You can use this command even if you have not registered
your nick yet. If your nick is already registered, you'll
need to identify yourself before using this command. Type
/msg NickServ HELP IDENTIFY for more information. This
last may be not possible on your IRC network.

It is recommended to use this command with a non-registered
nick because it will be registered automatically when
using this command. You may use it with a registered nick (to
change your group) only if your network administrators allowed
it.

You can only be in one group at a time. Group merging is
not possible.

Note: all the nicknames of a group have the same password.

IDENTIFY

Syntax: /msg NickServ IDENTIFY password

Syntax: IDENTIFY password

Tells NickServ that you are really the owner of this
nick. Many commands require you to authenticate yourself
with this command before you use them. The password
should be the same one you sent with the REGISTER
command.

LOGOUT

Syntax: /msg NickServ LOGOUT

Syntax: LOGOUT

This reverses the effect of the IDENTIFY command, i.e.
make you not recognized as the real owner of the nick
anymore. Note, however, that you won't be asked to reidentify
yourself.

DROP

Syntax: /msg NickServ DROP [nickname]

Syntax: DROP [nickname]

Drops your nickname from the NickServ database. A nick
that has been dropped is free for anyone to re-register.

You may drop a nick within your group by passing it
as the nick parameter.

In order to use this command, you must first identify
with your password (/msg NickServ HELP IDENTIFY for more
information).

ACCESS

Syntax: /msg NickServ ACCESS ADD mask

Syntax: ACCESS ADD mask
         ACCESS DEL mask
         ACCESS LIST

Modifies or displays the access list for your nick. This
is the list of addresses which will be automatically
recognized by NickServ as allowed to use the nick. If
you want to use the nick from a different address, you
need to send an IDENTIFY command to make NickServ
recognize you.

Examples:

     ACCESS ADD anyone@*.bepeg.com
         Allows access to user anyone from any machine in
         the bepeg.com domain.

     ACCESS DEL anyone@*.bepeg.com
         Reverses the previous command.

     ACCESS LIST
         Displays the current access list.

SET

Syntax: /msg NickServ SET option parameters

Syntax: SET option parameters

Sets various nickname options. option can be one of:

     DISPLAY    Set the display of your group in Services
     PASSWORD   Set your nickname password
     LANGUAGE   Set the language Services will use when
                    sending messages to you
     URL        Associate a URL with your nickname
     EMAIL      Associate an E-mail address with your nickname
     ICQ        Associate an ICQ number with your nickname
     GREET      Associate a greet message with your nickname
     KILL       Turn protection on or off
     SECURE     Turn nickname security on or off
     PRIVATE    Prevent your nickname from appearing in a
                    /msg NickServ LIST
     HIDE       Hide certain pieces of nickname information
     MSG        Change the communication method of Services
     AUTOOP     Should services op you automatically.

In order to use this command, you must first identify
with your password (/msg NickServ HELP IDENTIFY for more
information).

Type /msg NickServ HELP SET option for more information
on a specific option.

SET DISPLAY

Syntax: /msg NickServ SET DISPLAY new-display

Syntax: SET DISPLAY new-display

Changes the display used to refer to your nickname group in
Services. The new display MUST be a nick of your group.

SET PASSWORD

Syntax: /msg NickServ SET PASSWORD new-password

Syntax: SET PASSWORD new-password

Changes the password used to identify you as the nick's
owner.

SET LANGUAGE

Syntax: /msg NickServ SET LANGUAGE number

Syntax: SET LANGUAGE number

Changes the language Services uses when sending messages to
you (for example, when responding to a command you send).
number should be chosen from the following list of
supported languages:

SET URL

Syntax: /msg NickServ SET URL url

Syntax: SET URL url

Associates the given URL with your nickname. This URL
will be displayed whenever someone requests information
on your nick with the INFO command.

SET EMAIL

Syntax: /msg NickServ SET EMAIL address

Syntax: SET EMAIL address

Associates the given E-mail address with your nickname.
This address will be displayed whenever someone requests
information on the nickname with the INFO command.

SET HIDE

Syntax: /msg NickServ SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}

Syntax: SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}

Allows you to prevent certain pieces of information from
being displayed when someone does a NickServ INFO on your
nick. You can hide your E-mail address (EMAIL), last seen
user@host mask (USERMASK), your services access status
(STATUS) and last quit message (QUIT).
The second parameter specifies whether the information should
be displayed (OFF) or hidden (ON).

SET ICQ

Syntax: /msg NickServ SET ICQ number

Syntax: SET ICQ number

Associates the given ICQ number with your nickname. This
number will be displayed whenever someone requests
information on your nick with the INFO command.

SET GREET

Syntax: /msg NickServ SET GREET message

Syntax: SET GREET message

Makes the given message the greet of your nickname, that
will be displayed when joining a channel that has GREET
option enabled, provided that you have the necessary
access on it.

SET KILL

Syntax: /msg NickServ SET KILL {ON | QUICK | IMMED | OFF}

Syntax: SET KILL {ON | QUICK | IMMED | OFF}

Turns the automatic protection option for your nick
on or off. With protection on, if another user
tries to take your nick, they will be given one minute to
change to another nick, after which NickServ will forcibly change
their nick.

If you select QUICK, the user will be given only 20 seconds
to change nicks instead of the usual 60. If you select
IMMED, user's nick will be changed immediately without being
warned first or given a chance to change their nick; please
do not use this option unless necessary. Also, your
network's administrators may have disabled this option.

SET SECURE

Syntax: /msg NickServ SET SECURE {ON | OFF}

Syntax: SET SECURE {ON | OFF}

Turns NickServ's security features on or off for your
nick. With SECURE set, you must enter your password
before you will be recognized as the owner of the nick,
regardless of whether your address is on the access
list. However, if you are on the access list, NickServ
will not auto-kill you regardless of the setting of the
KILL option.

SET PRIVATE

Syntax: /msg NickServ SET PRIVATE {ON | OFF}

Syntax: SET PRIVATE {ON | OFF}

Turns NickServ's privacy option on or off for your nick.
With PRIVATE set, your nickname will not appear in
nickname lists generated with NickServ's LIST command.
(However, anyone who knows your nickname can still get
information on it using the INFO command.)

UPDATE

Syntax: /msg NickServ UPDATE

Syntax: UPDATE

Updates your current status, i.e. it checks for new memos,
sets needed chanmodes (ModeonID) and updates your vhost and
your userflags (lastseentime, etc).

SET HIDE

Syntax: /msg NickServ SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}

Syntax: SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}

Allows you to prevent certain pieces of information from
being displayed when someone does a NickServ INFO on your
nick. You can hide your E-mail address (EMAIL), last seen
user@host mask (USERMASK), your services access status
(STATUS) and last quit message (QUIT).
The second parameter specifies whether the information should
be displayed (OFF) or hidden (ON).

SET MSG

Syntax: /msg NickServ SET MSG {ON | OFF}

Syntax: SET MSG {ON | OFF}

Allows you to choose the way Services are communicating with
you. With MSG set, Services will use messages, else they'll
use notices.

RECOVER

Syntax: /msg NickServ RECOVER nickname [password]

Syntax: RECOVER nickname [password]

Allows you to recover your nickname if someone else has
taken it; this does the same thing that NickServ does
automatically if someone tries to use a kill-protected
nick.

When you give this command, NickServ will bring a fake
user online with the same nickname as the user you're
trying to recover your nick from. This causes the IRC
servers to disconnect the other user. This fake user will
remain online for NickServ to ensure that the other
user does not immediately reconnect; after that time, you
can reclaim your nick. Alternatively, use the RELEASE
command (/msg NickServ HELP RELEASE) to get the nick
back sooner.

In order to use the RECOVER command for a nick, your
current address as shown in /WHOIS must be on that nick's
access list, you must be identified and in the group of
that nick, or you must supply the correct password for
the nickname.

RELEASE

Syntax: /msg NickServ RELEASE nickname [password]

Syntax: RELEASE nickname [password]

Instructs NickServ to remove any hold on your nickname
caused by automatic kill protection or use of the RECOVER
command. This holds lasts for NickServ;
this command gets rid of them sooner.

In order to use the RELEASE command for a nick, your
current address as shown in /WHOIS must be on that nick's
access list, you must be identified and in the group of
that nick, or you must supply the correct password for
the nickname.

GHOST

Syntax: /msg NickServ GHOST nickname [password]

Syntax: GHOST nickname [password]

Terminates a "ghost" IRC session using your nick. A
"ghost" session is one which is not actually connected,
but which the IRC server believes is still online for one
reason or another. Typically, this happens if your
computer crashes or your Internet or modem connection
goes down while you're on IRC.

In order to use the GHOST command for a nick, your
current address as shown in /WHOIS must be on that nick's
access list, you must be identified and in the group of
that nick, or you must supply the correct password for
the nickname.

INFO

Syntax: /msg NickServ INFO nickname [ALL]

Syntax: INFO nickname [ALL]

Displays information about the given nickname, such as
the nick's owner, last seen address and time, and nick
options. If you are identified for the nick you're
getting information for and ALL is specified, you will
be shown all the information; regardless of whether
it's hidden or not.

LIST

Syntax: /msg NickServ LIST pattern

Syntax: LIST pattern

Lists all registered nicknames which match the given
pattern, in nick!user@host format. Nicks with the
PRIVATE option set will not be displayed.
Note that a pattern preceding with a '#' specifies a range.

Examples:

     LIST *!joeuser@foo.com
         Lists all nicks owned by joeuser@foo.com.

     LIST *Bot*!*@*
         Lists all registered nicks with Bot in their
         names (case insensitive).

     LIST *!*@*.bar.org
         Lists all nicks owned by users in the bar.org
         domain.

     LIST #50-100
         Lists nicks numbers 50-100

ALIST

Syntax: /msg NickServ ALIST [level]

Syntax: ALIST [level]

Lists all channels you have access on. Optionally, you can specify
a level in XOP or ACCESS format. The resulting list will only
include channels where you have the given level of access.

Examples:
     ALIST Founder
         Lists all channels where you have Founder
         access.

     ALIST AOP
         Lists all channels where you have AOP
         access or greater.

     ALIST 10
         Lists all channels where you have level 10
         access or greater.

Channels that have the NOEXPIRE option set will be
prefixed by an exclamation mark.

GLIST

Syntax: /msg NickServ GLIST

Syntax: GLIST

Lists all nicks in your group.

STATUS

Syntax: /msg NickServ STATUS nickname...

Syntax: STATUS nickname...

Returns whether the user using the given nickname is
recognized as the owner of the nickname. The response has
this format:

     nickname status-code

where nickname is the nickname sent with the command, and
status-code is one of the following:

     0 - no such user online or nickname not registered
     1 - user not recognized as nickname's owner
     2 - user recognized as owner via access list only
     3 - user recognized as owner via password identification

Up to sixteen nicknames may be sent with each command; the
rest will be ignored. If no nickname is given, your status
will be returned.

SENDPASS

Syntax: /msg NickServ SENDPASS nickname

Syntax: SENDPASS nickname

Send the password of the given nickname to the e-mail address
set in the nickname record. This command is really useful
to deal with lost passwords.

May be limited to IRC operators on certain networks.

This command is unavailable when encryption is enabled.

EXPIRES

Nicknames that are not used anymore are subject to
the automatic expiration, i.e. they will be deleted
after %d days if not used.

SERVADMIN HELP

Services admins can also drop any nickname without needing
to identify for the nick, and may view the access list for
any nickname (/msg NickServ ACCESS LIST nick).

SERVADMIN LOGOUT

Syntax: /msg NickServ LOGOUT [nickname [REVALIDATE]]

Syntax: LOGOUT [nickname [REVALIDATE]]

Without a parameter, reverses the effect of the IDENTIFY
command, i.e. make you not recognized as the real owner of the nick
anymore. Note, however, that you won't be asked to reidentify
yourself.

With a parameter, does the same for the given nick. If you
specify REVALIDATE as well, Services will ask the given nick
to re-identify. This use limited to Services admins.

SERVADMIN DROP

Syntax: /msg NickServ DROP [nickname]

Syntax: DROP [nickname]

Without a parameter, drops your nickname from the
NickServ database.

With a parameter, drops the named nick from the database.
You may drop any nick within your group without any
special privileges. Dropping any nick is limited to
Services admins.

SERVADMIN LIST

Syntax: /msg NickServ LIST pattern [FORBIDDEN] [SUSPENDED] [NOEXPIRE] [UNCONFIRMED]

Syntax: LIST pattern [FORBIDDEN] [SUSPENDED] [NOEXPIRE] [UNCONFIRMED]

Lists all registered nicknames which match the given
pattern, in nick!user@host format. Nicks with the PRIVATE
option set will only be displayed to Services admins. Nicks
with the NOEXPIRE option set will have a ! appended to
the nickname for Services admins.

If the FORBIDDEN, SUSPENDED, NOEXPIRE or UNCONFIRMED options are given, only
nicks which, respectively, are FORBIDDEN, SUSPENDED, UNCONFIRMED or have the
NOEXPIRE flag set will be displayed. If multiple options are
given, all nicks matching at least one option will be displayed.
These options are limited to Services admins.

Examples:

     LIST *!joeuser@foo.com
         Lists all registered nicks owned by joeuser@foo.com.

     LIST *Bot*!*@*
         Lists all registered nicks with Bot in their
         names (case insensitive).

     LIST * NOEXPIRE
         Lists all registered nicks which have been set to
         not expire.

SERVADMIN ALIST

Syntax: /msg NickServ ALIST [nickname] [level]

Syntax: ALIST [nickname] [level]

With no parameters, lists channels you have access on. With
one parameter, lists channels that nickname has access
on. With two parameters lists channels that nickname has
level access or greater on.

This use limited to Services admins.

SERVADMIN GLIST

Syntax: /msg NickServ GLIST [nickname]

Syntax: GLIST [nickname]

Without a parameter, lists all nicknames that are in
your group.

With a parameter, lists all nicknames that are in the
group of the given nick.
This use limited to Services admins.

SERVADMIN GETPASS

Syntax: /msg NickServ GETPASS nickname

Syntax: GETPASS nickname

Returns the password for the given nickname. Note that
whenever this command is used, a message including the
person who issued the command and the nickname it was used
on will be logged and sent out as a WALLOPS/GLOBOPS.

This command is unavailable when encryption is enabled.

SERVADMIN FORBID

Syntax: /msg NickServ FORBID nickname [reason]

Syntax: FORBID nickname [reason]

Disallows a nickname from being registered or used by
anyone. May be cancelled by dropping the nick.

On certain networks, reason is required.

SERVADMIN INFO

Services admins may use the ALL parameter with any nick.

SASET

Syntax: /msg NickServ SASET nickname option parameters.

Syntax: SASET nickname option parameters.

Sets various nickname options. option can be one of:

     DISPLAY    Set the display of the group in Services
     PASSWORD   Set the nickname password
     URL        Associate a URL with the nickname
     EMAIL      Associate an E-mail address with the nickname
     ICQ        Associate an ICQ number with the nickname
     GREET      Associate a greet message with the nickname
     KILL       Turn protection on or off
     SECURE     Turn nickname security on or off
     PRIVATE    Prevent the nickname from appearing in a
                    /msg NickServ LIST
     HIDE       Hide certain pieces of nickname information
     MSG        Change the communication method of Services
     NOEXPIRE   Prevent the nickname from expiring
     AUTOOP     Turn autoop on or off
     LANGUAGE   Set the language Services will use when
                sending messages to nickname

Type /msg NickServ HELP SASET option for more information
on a specific option. The options will be set on the given
nickname.

SASET DISPLAY

Syntax: /msg NickServ SASET nickname DISPLAY new-display

Syntax: SASET nickname DISPLAY new-display

Changes the display used to refer to the nickname group in
Services. The new display MUST be a nick of the group.

SASET PASSWORD

Syntax: /msg NickServ SASET nickname PASSWORD new-password

Syntax: SASET nickname PASSWORD new-password

Changes the password used to identify as the nick's owner.

SASET URL

Syntax: /msg NickServ SASET nickname URL url

Syntax: SASET nickname URL url

Associates the given URL with the nickname. This URL
will be displayed whenever someone requests information
on the nick with the INFO command.

SASET EMAIL

Syntax: /msg NickServ SASET nickname EMAIL address

Syntax: SASET nickname EMAIL address

Associates the given E-mail address with the nickname.

SASET ICQ

Syntax: /msg NickServ SASET nickname ICQ number

Syntax: SASET nickname ICQ number

Associates the given ICQ number with the nickname. This
number will be displayed whenever someone requests
information on the nick with the INFO command.

SASET GREET

Syntax: /msg NickServ SASET nickname GREET message

Syntax: SASET nickname GREET message

Makes the given message the greet of the nickname, that
will be displayed when joining a channel that has GREET
option enabled, provided that the user has the necessary
access on it.

SASET KILL

Syntax: /msg NickServ SASET nickname KILL {ON | QUICK | IMMED | OFF}

Syntax: SASET nickname KILL {ON | QUICK | IMMED | OFF}

Turns the automatic protection option for the nick
on or off. With protection on, if another user
tries to take the nick, they will be given one minute to
change to another nick, after which NickServ will forcibly change
their nick.

If you select QUICK, the user will be given only 20 seconds
to change nicks instead of the usual 60. If you select
IMMED, user's nick will be changed immediately without being
warned first or given a chance to change their nick; please
do not use this option unless necessary. Also, your
network's administrators may have disabled this option.

SASET SECURE

Syntax: /msg NickServ SASET nickname SECURE {ON | OFF}

Syntax: SASET nickname SECURE {ON | OFF}

Turns NickServ's security features on or off for your
nick. With SECURE set, you must enter your password
before you will be recognized as the owner of the nick,
regardless of whether your address is on the access
list. However, if you are on the access list, NickServ
will not auto-kill you regardless of the setting of the
KILL option.

SASET PRIVATE

Syntax: /msg NickServ SASET nickname PRIVATE {ON | OFF}

Syntax: SASET nickname PRIVATE {ON | OFF}

Turns NickServ's privacy option on or off for the nick.
With PRIVATE set, the nickname will not appear in
nickname lists generated with NickServ's LIST command.
(However, anyone who knows the nickname can still get
information on it using the INFO command.)

SASET HIDE

Syntax: /msg NickServ SASET nickname HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}

Syntax: SASET nickname HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}

Allows you to prevent certain pieces of information from
being displayed when someone does a NickServ INFO on the
nick. You can hide the E-mail address (EMAIL), last seen
user@host mask (USERMASK), the services access status
(STATUS) and last quit message (QUIT).
The second parameter specifies whether the information should
be displayed (OFF) or hidden (ON).

SASET MSG

Syntax: /msg NickServ SASET nickname MSG {ON | OFF}

Syntax: SASET nickname MSG {ON | OFF}

Allows you to choose the way Services are communicating with
the given user. With MSG set, Services will use messages,
else they'll use notices.

SASET NOEXPIRE

Syntax: /msg NickServ SASET nickname NOEXPIRE {ON | OFF}

Syntax: SASET nickname NOEXPIRE {ON | OFF}

Sets whether the given nickname will expire. Setting this
to ON prevents the nickname from expiring.

SASET AUTOOP

Syntax: /msg NickServ SASET nickname AUTOOP {ON | OFF}

Syntax: SASET nickname AUTOOP {ON | OFF}

Sets whether the given nickname will be opped automatically.
Set to ON to allow ChanServ to op the given nickname
automatically when joining channels.

SASET LANGUAGE

Syntax: /msg NickServ SASET nickname LANGUAGE number

Syntax: SASET nickname LANGUAGE number

Changes the language Services uses when sending messages to
nickname (for example, when responding to a command he sends).
number should be chosen from a list of supported languages
that you can get by typing /msg NickServ HELP SET LANGUAGE.

How to Install eMech - EnergyMech

2011-09-23T21:56:00.000-07:00

How to Install EnergyMech

wget http://shkarko.zemra.org/emech-2.9.4.tar.gz
tar -zxvf emech-2.9.4.tar.gz
cd emech-2.9.4
./configure
make
make install
cp sample.conf mech.set
configure your mech.set file
./mech

How to Install Emech

wget http://www.energymech.net/files/emech-3.0.3.tar.gz

tar -zxvf emech-3.0.3.tar.gz

rm -rf emech-3.0.3.tar.gz

cd emech-3.0.3

./configure

make clean install

cp sample.conf mech.conf

configure your mech.conf file

edit checkmech line cd /home/user/emech*/

./energymech

How to Install Emech

wget http://www.energymech.net/files/emech-2.8.5-freebsd-static.tar.gz

tar -zxvf emech-2.8.5-freebsd-static.tar.gz

rm -rf emech-2.8.5-freebsd-static.tar.gz

cd emech-2.8.5-freebsd-static

./genuser

enter handle (Nickname first than HOST/IP)

comment this line on checkmech file: # echo "You havent edited checkmech yet!!"

change this line cd /home/user/mechfolder

create mech.set file

add your mech users

./mech (if you add more than one energymech you should now run ./genuser *mechfile)

run ./mech

Energymech config file

# Sample EnergyMech configuration file
# v2.8.2 - HitMan
#
# Note - Lines starting with '#' are comments and ignored by the bot.

##### Linking #####
# EnergyMechs can link(-help LINK) to one another to perform such features
# as DCC PartyLine, Remote Command Execution (-help CMD), and Ops/Protection
# (Add linked bots to eachother at level 200). This section is optional,
# bots running in the same config file are automaticly linked.

# Entity Name: In order to link to other bots, your bot must
#              have a unique entity name. -CHANGE THIS-
ENTITY        mechbot

# Link Password: A password for linking. -CHANGE THIS-
LINKPASS      linkpassword

# Link Port: A port the bot will listen on for linking, telnet, 
#            and pipeuser(http://www.energymech.net/docs/pipeuser.html)
#            This has to be above 1024, and some firewalls, noteably
#            IP Masquerade/NAT may block this.
LINKPORT      6667

# An example link configuration, here you have an ENTITY called ``hismech'' 
# and its LINKPASS  is ``a1b2c3''. It is running on ``mech.host.net'' and
# it's LINKPORT is 49152.
LINK          hismech linkpassword 67.43.238.222 6667

# Another example, the entity ``hermech'' is not listening on any port
# (missing or non-working LINKPORT in config), so it does not matter
# what host it is on as well, thus "0 0" at the end(-help LINK).
LINK          hermech linkpassword 67.43.238.222 6667

# Automatic Linking: Uncomment this to enable auto-linking. This will
#                    cause the mech to try and link to all bots in it's
#                    list, until all are present.
AUTOLINK

##### Server List ####
# Some undernet servers to connect to... You can use server names is you wish, 
# but putting the IP's here instead of host names speeds up connects (alot).
# Servers are global, all mechs in the same process uses the same server list.
#
SERVER 67.43.238.222       6667    # 67.43.238.222



##### Bot 1 Configuration #####
# In EnergyMech, you can have multiple bots on IRC from the same config
# file/process. Traditionaly, the spawn command was used, however, that 
# command has been removed in 2.8.2 and above due to abuse. You can still
# specify more than one bot in the config file as shown.

# Nick for the bot.
NICK          Gonxhe

# The file we use to store the userlist. Note you will have to generate
# this with a command such as ./genuser emech.users
USERFILE      emech.users

# All commands begin with this character.
CMDCHAR       -

# Register on IRC with this username (emech@xxxxxxxx). Note that if your
# machine is running identd, it will always be your username.
LOGIN         emech

# Display this in the "Real Name" field
IRCNAME       Vizitor nga Chat.KnaQu.Org

# User modes for the bot
MODES         +i-ws

# If you want to run the bot on a virtual host, uncomment
# the below line and set it.
VIRTUAL       has.hacked.ur.eggdr0pz.us

# If you compiled with SEEN support and decide not to use it, uncomment this.
#NOSEEN

# Channel-Independant toggles and sets. See the -REPORT command for a full
# listing.
HASONOTICE  # Yes for Undernet.
TOG CC          1       # We want the bot to require command character
TOG CLOAK       1       # Ignore CTCP's from non-users? Yes.
TOG SPY         1       # Tell who is executing what in the partyline.
SET OPMODES     6       # How many modes in a line? 6 on undernet...
SET BANMODES    6       # How many bans in a line? 6 on undernet...
SET CTIMEOUT    90      # Server connection timeout
SET CDELAY      30      # Delay between connection attempts

# Basic channel setup. You can have as many of these as your server
# supports. See the -REPORT command for a listing.
CHANNEL         #emech      # Channel name
TOG PUB         1       # Allow public(in-channel) commands? Yes.
TOG MASS        1       # Do mass-mode/kick/ban checks...
TOG SHIT        1       # Activate the shitlist for this channel
TOG PROT        1       # Activate protection of users
TOG ENFM        0       # Dont enforce channel modes.
SET MDL         7       # How many -o before killing the guy?
SET MKL         7       # How many kicks?
SET MBL         7       # And how many Bans?
SET MPL         1       # What to do with massmoders?
#                       0 = nothing,
#                       1 = kick the bastard,
#                       2 = kickban 'em,
#                       3 = kickban & shitlist them.
##### END BOT 1 #####

How to Install psyBNC

2011-09-23T21:54:00.001-07:00

How To Install psyBNC

wget http://shkarko.zemra.org/psyBNC-2.3.2-7.tar.gz
tar zxvf psyBNC-2.3.2-7.tar.gz
cd psyBNC
make menuconfig

Country Name []:AU

State/Province [Somewhere]:Vic

Locality Name (eg, city) []:Melbourne

Organization Name (eg, company) [tCl]:Home

Organizational Unit Name (eg, section) [psyBNC]:psyBNC

Common Name (Full domain of your server) []:irc.zemra.org

pico psybnc.conf
./psybnc

How To Install and Configure EggDrop

2011-09-23T21:53:00.000-07:00

How To Install EggDrop

wget http://shkarko.zemra.org/eggdrop1.6.20.tar.gz
tar zxvf eggdrop1.6.20.tar.gz
cd eggdrop1.6.20
./configure
make config
make
make install
cd ~/eggdrop
./eggdrop -m eggdrop.conf

How To Configure EggDrop
Si Konfigurohet EggDrop



#! ./eggdrop

### Core Settings ###
set admin "DeviL"
set nick "ZemraBot"
set altnick "ZemraBot-"
set realname "www.Zemra.Org EggDrop"
set network "DALnet"
set net-type "3"
set init-server { putserv "mode ZemraBot +i" }
set default-port 6667
set servers {
irc.zemra.org
irc.knaqu.org

}

set timezone "GMT"
set offset "0"
set env(TZ) "$timezone $offset"
set my-hostname "EggDrop.Zemra.Org"
set my-ip "77.88.99.100"

### Logfile Settings ###
set max-logs 5
set max-logsize 0
set quick-logs 0
logfile mcobxs * "logs/ZemraBot.log"
logfile jkp #ALbaChat "logs/#ALbaChat.log"
set log-time 1
set keep-all-logs 1
set logfile-suffix ""
set switch-logfiles-at 300
set quiet-save 0

### Console Settings ###
set console "mkcobxs"

### File & Directory Settings ###
set userfile "ZemraBot.user"
set pidfile "pid.ZemraBot"
set chanfile "ZemraBot.chan"
set force-expire 0
set share-greet 0
set use-info 1
set sort-users 0
set help-path "help/"
set text-path "text/"
set temp-path "/tmp"
set motd "text/motd"
set telnet-banner "text/banner"
set userfile-perm 0600
set mod-path "modules/"

### BotNet Settings ###
set botnet-nick "ZemraBot"
listen 2010 all
set remote-boots 0
set share-unlinks 0
set protect-telnet 1
set dcc-sanitycheck 1
set ident-timeout 0
set require-p 1
set open-telnets 0
set stealth-telnets 0
set use-telnet-banner 0
set connect-timeout 30
set dcc-flood-thr 3
set telnet-flood 5:60
set paranoid-telnet-flood 1
set resolve-timeout 15

### Channel Settings ###
loadmodule channels
set global-flood-chan 4:5
set global-flood-deop 0:0
set global-flood-kick 0:0
set global-flood-join 4:05
set global-flood-ctcp 2:02
set global-flood-nick 5:20
set global-aop-delay 0:00
set global-idle-kick 0
set global-chanmode "nt"
set global-stopnethack-mode 0
set global-revenge-mode 0
set global-ban-time 0
set global-exempt-time 60
set global-invite-time 60

set global-chanset {
-autoop -autovoice
-bitch -cycle
+dontkickops -dynamicbans
+dynamicexempts +dynamicinvites
-enforcebans -greet
-inactive +nodesynch
+protectfriends +protectops
-revenge -revengebot
-secret +seen
+shared -statuslog
+userbans +userexempts
+userinvites -protecthalfops
-autohalfop
}

channel add #ALbaChat {
chanmode "+tn"
idle-kick 0
flood-chan 5:4
flood-join 5:10
flood-ctcp 3:60
flood-deop 0:0
flood-kick 0:0
}
channel set #ALbaChat -enforcebans -dynamicbans -autoop -autovoice +protectops +protectfriends

### Advanced Settings ###
set ignore-time 5
set hourly-updates 00
set owner "DeviL"
set notify-newusers "DeviL"
set default-flags "hp"
set whois-fields "url birthday"
set die-on-sighup 0
set die-on-sigterm 1
unbind dcc n tcl *dcc:tcl
unbind dcc n set *dcc:set
set must-be-owner 1
unbind dcc n simul *dcc:simul
set max-dcc 50
set enable-simul 1
set allow-dk-cmds 1
set dupwait-timeout 5

### Module Settings ###
loadmodule dns
loadmodule transfer
loadmodule share
loadmodule server
loadmodule ctcp
loadmodule irc
loadmodule notes
loadmodule console
loadmodule blowfish
checkmodule blowfish
loadmodule uptime

set keep-nick 1
set strict-host 0
set quiet-reject 1
set lowercase-ctcp 0
set answer-ctcp 3
set flood-msg 5:5
set flood-ctcp 3:60
set never-give-up 1
set strict-servernames 0
set server-cycle-wait 60
set server-timeout 60
set servlimit 0
set check-stoned 1
set use-console-r 0
set debug-output 0
set serverror-quit 1
set max-queue-msg 300
set trigger-on-ignore 0
set double-mode 0
set double-server 0
set double-help 0
set optimize-kicks 1
set stack-limit 4
set ctcp-mode 0
set bounce-bans 1
set bounce-modes 0
set max-bans 100
set max-modes 30
set kick-fun 0
set ban-fun 0
set learn-users 0
set wait-split 600
set wait-info 180
set mode-buf-length 200
bind msg - ident *msg:ident
bind msg - addhost *msg:addhost
set no-chanrec-info 0
set bounce-exempts 0
set bounce-invites 0
set max-exempts 20
set max-invites 20
set prevent-mixing 1
set max-dloads 3
set dcc-block 1024
set copy-to-tmp 1
set xfer-timeout 30
set share-compressed 1
set max-notes 50
set note-life 60
set allow-fwd 0
set notify-users 1
set notify-onjoin 1
set console-autosave 1
set force-channel 0
set info-party 0

### Script Settings ###
source scripts/alltools.tcl
source scripts/action.fix.tcl
source scripts/cmd_resolve.tcl
source scripts/compat.tcl

AntiRandom Module

2011-09-23T21:50:00.000-07:00

How To Install AntiRandom

1. wget http://www.unrealircd.com/modules/dl/u3/src/36/AntiRandom.tar.gz
2. tar -xvf AntiRandom.tar.gz
3. /build
4. add on your unrealircd.conf
loadmodule "src/modules/antirandom.so";
5. (add this code to your unrealircd.conf)
set { antirandom { threshold 5; ban-action gline; ban-time 2m; ban-reason "Ju lutem ndryshoni Nick/Ident ose Realname - ose provoni http://Chat.Zemra.Org/"; fullstatus-on-load yes; show-failedconnects yes; except-hosts { }; }; };
6. ./rehash your IRCD

BLSB Module

2011-09-23T21:48:00.001-07:00

How to Install BLSB NeoStats Module

1. cd NeoStats3.0/modules

2. wget

http://shkarko.zemra.org/modules/neostats/BLSB-3.0.a4-66.tar.gz
3. tar -xvf BLSB-3.0.a4-66.tar.gz
4. cd BLSB-3.0.a4-66

 5. ./configure

6. make

7. make install

8. on IRC type: /msg neostats load blsb

BOPM Module

2011-09-23T21:47:00.000-07:00

How To Install BOPM Module

1. wget http://ircd.zemra.org/irc/bopm-3.1.3.tar.gz
2. tar -xvf bopm-3.1.3.tar.gz
3. cd bopm-3.1.3
4. ./configure
5. make
6. make install
7. cd
8. cd bopm/etc
9. pico bopm.conf

/* This is a modified bopm.conf
 * http://www.zemra.org
 * LAST MODIFIED: 2010-11-20
 */

options {
 /* Full path and filename for file storing the process ID */
 pidfile = "/home/EviL/bopm/bopm.pid";

 /* seconds to store the IP address of hosts */
#    negcache = 3600;

 /* Amount of file descriptors to allocate to asynchronous DNS */
 dns_fdlimit = 64;

 /* full path and filename of scan logfile */
#    scanlog = "/home/EviL/bopm/scan.log";
};

IRC {
 /* IP to bind to for the IRC connection */
 vhost = "72.20.42.110";

 /* Nickname for BOPM to use */
 nick = "TheHawk";

 /* Text to appear in the "realname" field of BOPM's whois output */
 realname = "Open Proxy Monitoring";

 /* If you don't have an identd running, what username to use */
 username = "nix";

 /* Hostname (or IP) of the IRC server */
 server = "72.20.42.110";

 /* Password used to connect to the IRC server (PASS) */
#    password = "secret";

 /* Connect to IRC server via this port */
 port = 6667; 

 /* Command to identify to NickServ */
#    nickserv = "privmsg nickserv :identify <password>";

 /* The username and password needed for BOPM to oper up */
 oper = "BOPM bopmoperpass";

 /* with the following modes this BOPM will see ALL network Connections
 * See Unreal documentation for more information on user modes
 */
 mode = "+s +cF";

 /* Specify BOPM control channel(s) */
 channel {
 /* Channel name. */
 name = "#Staff";

 /* Channel key */
 key = "<channel-key>";

 /* command used to ask chanserv for invite */
#        invite = "privmsg chanserv :invite #bopm";
 };

 /* connregex is a POSIX regular expression used to parse connection
 * (+c) notices from the ircd. The complexity of the expression should
 * be kept to a minimum so load is @ a minimum even during 'heavy' traffic */

 /* Unreal in HCN mode */
#    connregex = "\\*\\*\\* Notice -- Client connecting: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*";
 connregex = "\\*\\*\\* Notice -- Client connecting[.A-Za-z0-9 ]*: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*";

 /* default kline
 *  %n User's nick
 *  %u User's username     - REMEMBER!
 *  %h User's irc hostname - bots (& blacklists) don't necessarily have (contain) hostnames
 *  %i User's IP address   - but they ALWAYS have IPs */
 kline = "gline +*@%i 7d :Open Proxy found on your host.";

 /* Text to send on connection. Specify multiple with multiple lines. */
 perform = "PROTOCTL HCN";
};

OPM {

blacklist {
 name = "rbl.efnetrbl.org";
 type = "A record reply";
 reply {
 1 = "Open proxy";
 2 = "spamtrap666";
 3 = "spamtrap50";
 4 = "TOR exit server";
 5 = "Drones / Flooding";
 };
 ban_unknown = no;
 kline = "gline +*@%i 0 : 4An open proxy was detected in your host 1 - EFnetRBL ";
};

blacklist {
 name = "dnsbl.dronebl.org";
 type = "A record reply";
 reply {
 3 = "IRC Drone";
 4 = "Tor";
 5 = "Bottler";
 6 = "Unknown spambot or drone";
 7 = "DDOS Drone";
 8 = "SOCKS Proxy";
 9 = "HTTP Proxy";
 10 = "ProxyChain";
 };
 ban_unknown = no;
 kline = "gline +*@%i 0 : 4An open proxy was detected in your host 1 - DroneBL";
};

blacklist {
 name = "dnsbl.njabl.org";
 type = "A record reply";
 reply {
 2 = "Open Relay";
 4 = "Confirmed Spam Source";
 9 = "Open Proxy";
 };
 ban_unknown = no;
 kline = "gline +*@%i 0 : 4An open proxy was detected in your host 1 - NJABL";
};

blacklist {
 name = "dnsbl.swiftbl.org";
 type = "A record reply";
 reply {
 2 = "SOCKS Proxy";
 3 = "IRC Proxy";
 4 = "HTTP Proxy";
 5 = "IRC Drone";
 6 = "TOR";
 };
 ban_unknown = no;
 kline = "gline +*@%i 0 : 4An open proxy was detected in your host 1 - SwiftBL";
};

blacklist {
 name = "dnsbl.proxybl.org";
 type = "A record reply";
 reply {
 2 = "Open proxy";
 };
 ban_unknown = no;
 kline = "gline +*@%i 0 : 4An open proxy was detected in your host 1 - ProxyBL";
};

/* the next two entries might match too many IPs
 * so they're commented out for now
 */

/*
blacklist {
 name = "dnsbl-2.uceprotect.net";
 type = "A record reply";
 reply {
 2 = "Matched Entry";
 };
 ban_unknown = no;
 kline = "gline +*@%i 7d :uceprotect";
};

blacklist {
 name = "xbl.spamhaus.org";
 type = "A record reply";
 reply {
 4 = "CBL Detected Address"
 };
 ban_unknown = no;
 kline = "gline +*@%i 7d : 4An open proxy was detected in your host 1 - SpamhausXBL";
};
*/
 /* Pretend to send reports FROM */
#    dnsbl_from = "mybopm@myserver.example.com";

 /* Email address to send reports TO.  Specify multiple with multiple lines. */
#    dnsbl_to = "bopm-report@dronebl.org";

 /* Full path to your sendmail binary */
#    sendmail = "/usr/sbin/sendmail";
};

/* Exempt hosts matching (hostname or IP) strings from any form of scanning or dnsbl */
exempt {
 mask = "*!*@127.0.0.1";
};

exempt {
 mask = "*!*@72.20.42.*"; # Zemra.Org SHELL IP
};

12. cd ..
13. cd bin
14. ./bopm

Written by DeviL
www.Zemra.Org
Email: Info@Zemra.Org

FloodServ Module

2011-09-23T21:46:00.000-07:00

How To Install FloofServ Module



1. cd NeoStats3.0/modules

2. wget http://shkarko.zemra.org/Modules/NeoStats/FloodServ-3.0.a4-70.tar.gz

3. tar -xvf FloodServ-3.0.a4-70.tar.gz

4. cd FloodServ-3.0.a4-70

5. ./configure

6. make

7. make install

8. on IRC type: /msg neostats load floodserv

GamesServ Module

2011-09-23T21:45:00.000-07:00

How To Install GamesServ NeoStats Module

1. cd NeoStats3.0/modules

2. wget

http://shkarko.zemra.org/modules/neostats/GamesServ-3.0.1-60.tar.gz
3. tar -xvf GamesServ-3.0.1-60.tar.gz
4. cd GamesServ-3.0.1-60

 5. ./configure

6. make

7. make install

8. on IRC type: /msg neostats load

GamesServ

NetAdmins Module

2011-09-23T21:43:00.001-07:00

How to Install NetAdmins Module

1. cd Unreal3.2/src/modules 2. wget http://shkarko.zemra.org/Modules/UnrealIRCD/netadmins.c 3. cd ../.. 4. ./Config 5. make 6. make custommodule MODULEFILE=netadmins 7. On your unrealircd.conf, put this line loadmodule “src/modules/netadmins.so”;

Unrealircd.conf



set {

// Choose "no" here if you would like to allow

// netadmins to kill each other. Otherwise "yes".

netadmins-are-gods yes;

};

Noexpire Module

2011-09-23T21:42:00.000-07:00

How To Install NoExpire Module

1. cd anope-1.8.5 2. cd src/modules 3. wget http://shkarko.zemra.org/Modules/ns_noexpire.c 4. cd ../.. 5. make modules 6. make install 7. go to IRC and type /operserv modload ns_noexpire

Operjoin Module

2011-09-23T21:02:00.002-07:00

How to compile operjoin module

wget http://shkarko.zemra.org/modules/unrealircd/operjoin.tar.gz tar -xvf operjoin.tar.gz cp operjoin.c Unreal3.2/src/modules cd Unreal3.2 ./Config make or gmake make custommodule MODULEFILE=operjoin make install loadmodule "src/modules/modulename.so"; (add this line to your unrealircd.conf) /rehash your ircd

OPSB Module

2011-09-23T21:02:00.000-07:00

How To Install OPSB

 1. cd NeoStats3.0/modules

2. wget http://unix.oppserver.net/irc/ircd/neostats/OPSB-3.0.a3.tar.gz

3. tar -xvf OPSB-3.0.a3.tar.gz

4. cd OPSB-3.0.a3

5. ./configure

6. make

7. make install

8. on IRC type: /msg neostats load opsb

SecureServ

2011-09-23T21:01:00.000-07:00

How To Install SecureServ



1. cd NeoStats3.0/modules

2. wget http://shkarko.zemra.org/Modules/NeoStats/SecureServ-3.0.a3.tar.gz

3. tar -xvf SecureServ-3.0.a3.tar.gz

4. cd SecureServ-3.0.a3

5. ./configure

6. make

7. make install

8. on IRC type: /msg neostats load secureserv

UnrealIRCD

2011-09-23T21:00:00.000-07:00

How To Install UnrealIRCD

wget http://shkarko.zemra.org/Unreal3.2.8.1.tar.gz
tar xfz Unreal3.2.8.1.tar.gz
cd Unreal3.2
./Config



anti-spoof protection? No

directory with configuration files? hit enter

path to ircd binary? hit enter

hub or leaf? Hub

hostname? Type the subdomain created earlier

default permissions? 0600

SSL support? No (or Yes if you are a security addict)

IPv6 support? No

enable ziplinks? No (unless you're linking with another IRCD)

enable remote includes? No (again, unless you're linking)

enable prefixes? Yes (totally up to you)

listen backlog? 5 is fine, hit enter

nickname history? 2000 is fine, hit enter

max SendQ

length? hit enter

buffer pools? hit enter

file descriptors? hit enter

more parameters? hit enter

make ose gmake
cp doc/example.conf unrealircd.conf

now configure unrealircd.conf file

/*

* Unrealircd.conf by DeviL (Info@Zemra.Org).

*/

/* Type of comments */
#Comment type 1 (Shell type)
// Comment type 2(C++ style)
/* Comment type 3 (C Style) */
#those lines are ignored by the ircd.

/* FOR *NIX, uncomment the following 2lines: */
loadmodule "src/modules/commands.so";
loadmodule "src/modules/cloak.so";
#loadmodule "src/modules/antirandom.so";
#loadmodule "src/modules/hideserver.so";
#loadmodule "src/modules/nocolorumode.so";
#loadmodule "src/modules/antimoon.so";
#loadmodule "src/modules/m_privdeaf.so";

/* FOR Windows, uncomment the following 2 lines: */
//loadmodule "modules/commands.dll";
//loadmodule "modules/cloak.dll";

include "help.conf";
include "badwords.channel.conf";
include "badwords.message.conf";
include "badwords.quit.conf";
include "spamfilter.conf";

me
{
name "Irc.Zemra.Org";
info " - 12Zemra e Shqiptarit";
numeric 10;
};

admin {
"Server: Irc.Zemra.Org";
"Admin: «« 12Admin »»";
"E-Mail: 12Admin@Zemra.Org "; };

class clients
{
pingfreq 90;
maxclients 500;
sendq 1000000;
recvq 8000;
};

class servers
{
pingfreq 90;
maxclients 10; /* Max servers we can have linked at a time */
sendq 10000000;
connfreq 100; /* How many seconds between each connection attempt */
};

allow {

ip *@*;
hostname *@*.static.tpgi.com.au;
class clients;
maxperip 10;
};

listen 72.62.52.41:4444;
listen 72.62.52.41:6660-6669;
listen 72.62.52.41:8001-8005;

allow channel {
channel "#ALbaChat";
};
allow channel {
channel "#Ndihme";
};
allow channel {
channel "#Ops";
};

deny channel {
channel "*#*";
reason "Nuk lejohet hapja e kanaleve të reja! Për më shumë info, kontaktoni Administratorët e serverit!";
redirect "#ALbaChat";
};

link Services.Zemra.Org {
username *;
hostname 72.62.52.41;
bind-ip *;
port 4444;
hub *;
password-connect "Services";
password-receive "Services";
class servers;
options {
};
};
link Stats.Zemra.Org {
username *;
hostname 72.62.52.41;
bind-ip *;
port 4444;
hub *;
password-connect "Links";
password-receive "Links";
class servers;
options {
};
};

ulines {
Services.Zemra.Org;
Stats.Zemra.Org;
};

drpass {
restart "Restart";
die "Die";
};

log "ircd.log" {
/* Delete the log file and start a new one when it reaches 2MB, leave this out to always use the
same log */
maxsize 2097152;
flags {
oper;
kline;
connects;
server-connects;
kills;
errors;
sadmin-commands;
chg-commands;
oper-override;
spamfilter;
};
};

// This points the command /nickserv to the user NickServ who is connected to the set::services-server server
/*alias NickServ {
target "NickServ";
type services;
};*/

// If you want the command to point to the same nick as the command, you can leave the nick entry out
//alias ChanServ { type services; };

// Points the /statserv command to the user StatServ on the set::stats-server server
//alias StatServ { type stats; };

// Points the /superbot command to the user SuperBot
//alias SuperBot { type normal; };

/* Standard aliases */
alias nickserv { type services; };
alias ns { nick nickserv; type services; };
alias chanserv { type services; };
alias cs { nick chanserv; type services; };
alias memoserv { type services; };
alias ms { nick memoserv; type services; };
alias operserv { type services; };
alias os { nick operserv; type services; };
alias helpserv { type services; };
alias hs { nick helpserv; type services; };
alias irciihelp { type services; };
alias statserv { type services; };
alias ss { nick statserv; type services; };
alias botserv { type services; };
alias bs { nick botserv; type services; };
alias NickServ { type services; };
alias ChanServ { type services; };
alias OperServ { type services; };
alias HelpServ { type services; };
alias StatServ { type stats; };

alias "identify" {
format "^#" {
target "chanserv";
type services;
parameters "IDENTIFY %1-";
};
format "^[^#]" {
target "nickserv";
type services;
parameters "IDENTIFY %1-";
};
type command;
};

/* Standard aliases */
alias "services" {
format "^#" {
target "chanserv";
type services;
parameters "%1-";
};
format "^[^#]" {
target "nickserv";
type services;
parameters "%1-";
};
type command;
};

alias "identify" {
format "^#" {
target "chanserv";
type services;
parameters "IDENTIFY %1-";
};
format "^[^#]" {
target "nickserv";
type services;
parameters "IDENTIFY %1-";
};
type command;
};

/* This is an example of a real command alias */
/* This maps /GLINEBOT to /GLINE <parameter> 2d etc... */
alias "glinebot" {
format ".+" {
command "gline";
type real;
parameters "%1 +0 4Bots are not allowed in this server - 12Gline@Zemra.Org ";
};
type command;
};

tld {
mask *@*;
motd "ircd.motd";
rules "ircd.rules";
opermotd "ircd.opermotd";
};
ban nick {
mask "*Serv*";
reason "Reserved for Services";
};
ban ip {
mask 195.86.232.81;
reason "Delinked server";
};
ban server {
mask eris.berkeley.edu;
reason "Get out of here.";
};
ban user {
mask *tirc@*.saturn.bbn.com;
reason "Idiot";
};
ban realname {
mask "www.AlbaTok.com";
reason "Ndro Relaname";
};
ban realname {
mask "WwW.Tivendos.Net";
reason "Ndro Relaname";
};
except ban {
/* don't ban stskeeps */
mask *!*Zemra*@*;
};

deny dcc { filename "*sub7*"; reason "DCC Trojan..."; };
deny dcc { filename "*vbs*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };
deny dcc { filename "*bat*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };
deny dcc { filename "*com*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };
deny dcc { filename "*exe*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };

vhost {
vhost Operator.Zemra.Org;
from {
userhost *@*;
};
login operator;
password zemra;
};
vhost {
vhost Operatore.Zemra.Org;
from {
userhost *@*;
};
login operatore;
password zemra;
};

/* You can include other configuration files */
/* include "klines.conf"; */

/* Network configuration */
set {
network-name "Zemra";
default-server "Irc.Zemra.Org";
services-server "services.Zemra.Org";
stats-server "stats.zemra.Org";
help-channel "#Ndihme";
hiddenhost-prefix "Zemra";
prefix-quit " 12Vizitor nga 4«« ¤ 12www.Zemra.Org 4 ¤ »» ";
/* Cloak keys should be the same at all servers on the network.
* They are used for generating masked hosts and should be kept secret.
* The keys should be 3 random strings of 5-100 characters
* (10-20 chars is just fine) and must consist of lowcase (a-z),
* upcase (A-Z) and digits (0-9) [see first key example].
*/
cloak-keys {
"LCdRdwzb88hPkMdsdsmnGF3cbOv0b";
"mFFQaKFSjSl2dsdssf67cmmElq2uHqx";
"wHmk7pJULg8dfzxczOuhCLfp74MgQId";
};

/* on-oper host */
hosts {
local "IRCop.Zemra.Org";
global "IRCop.Zemra.Org";
coadmin "Co-Admin.Zemra.Org";
admin "Admin.Zemra.Org";
servicesadmin "Services-Admin.Zemra.Org";
netadmin "NetAdmin.Zemra.Org";
host-on-oper-up "yes";
};
};

/* Server specific configuration */

set {
kline-address "GLine@Zemra.Org";
modes-on-connect "+icxvw";
auto-join "#ALbaChat";
modes-on-join "+ntrVCTfj 3:1 [5j#R1,7m#M5,2n#N1,7t#b]:3";
modes-on-oper "+Wxwgspq";
restrict-usermodes "icvwx";
snomask-on-oper "+cFfkejvGnNqsSo";
oper-auto-join "#ALbaChat,#Ndihme,#Ops,#Staff";
dns {
nameserver 127.0.0.1;
timeout 2s;
retries 2;
};
options {
hide-ulines;
/* You can enable ident checking here if you want */
identd-check;
flat-map;
allow-part-if-shunned;
fail-oper-warn;
show-connect-info;
};

maxchannelsperuser 15;

anti-spam-quit-message-time 10s;

static-quit " 12Vizitor nga 4«« ¤ 12www.Zemra.Org 4 ¤ »» ";

static-part "Client Parted from 4«« ¤ 12www.Zemra.Org 4 ¤ »» ";

// flat-map "Nuk keni access te mjafueshëm për komandën /map";

// flat-links "Nuk keni access te mjafueshëm për komandën /links.";

oper-only-stats "*";

/* Throttling: this example sets a limit of 3 connection attempts per 60s (per host). */
throttle {
connections 3;
period 60s;
};

/* Anti flood protection */
anti-flood {
nick-flood 2:60; /* 3 nickchanges per 60 seconds (the default) */
};

/* Spam filter */
spamfilter {
ban-time 1d; /* default duration of a *line ban set by spamfilter */
ban-reason "Spam/Advertising"; /* default reason */
virus-help-channel "#Ndihme"; /* channel to use for 'viruschan' action */
/* except "#Ndihme"; channel to exempt from filtering */
};
};

/*
* Unrealircd.conf by DeviL (Info@Zemra.Org).
* For any help visite http://www.Zemra.Org
*/

/*
* Unrealircd.conf by HitMan (Info@Zemra.Org).
*/

/* Type of comments */
#Comment type 1 (Shell type)
// Comment type 2(C++ style)
/* Comment type 3 (C Style) */
#those lines are ignored by the ircd.

/* FOR *NIX, uncomment the following 2lines: */
loadmodule "src/modules/commands.so";
loadmodule "src/modules/cloak.so";
loadmodule "src/modules/antirandom.so";
loadmodule "src/modules/hideserver.so";
loadmodule "src/modules/nocolorumode.so";
loadmodule "src/modules/antimoon.so";
loadmodule "src/modules/m_privdeaf.so";

/* FOR Windows, uncomment the following 2 lines: */
//loadmodule "modules/commands.dll";
//loadmodule "modules/cloak.dll";

include "help.conf";
include "badwords.channel.conf";
include "badwords.message.conf";
include "badwords.quit.conf";
include "spamfilter.conf";
include "oper.conf";
include "badnick.conf";
include "exception.conf";

me
{
name "Irc.Zemra.Org";
info " - 12Zemra e Shqiptarit";
numeric 10;
};

admin {
"Server: Irc.Zemra.Org";
"Admin: «« 12Admin »»";
"E-Mail: 12Admin@Zemra.Org "; };

class clients
{
pingfreq 90;
maxclients 500;
sendq 100000;
recvq 8000;
};

class servers
{
pingfreq 90;
maxclients 10; /* Max servers we can have linked at a time */
sendq 1000000;
connfreq 100; /* How many seconds between each connection attempt */
};

allow {
ip *@*;
hostname *@*.static.tpgi.com.au;
class clients;
maxperip 10;
};

listen 72.20.42.110:3366;
listen 72.20.42.110:6660-6669;
listen 72.20.42.110:8001-8005;

allow channel {
channel "#ALbaChat";
};
allow channel {
channel "#Ndihme";
};
allow channel {
channel "#Ops";
};

deny channel {
channel "*#*";
reason "Nuk lejohet hapja e kanaleve të reja! Për më shumë info, kontaktoni Administratorët e serverit!";
redirect "#ALbaChat";
};
set {
antirandom {
threshold 5;
ban-action gzline;
ban-time 100d;
ban-reason " 4Ju lutemi ri-lidhuni prej 12http://Chat.Zemra.Org/ ";
fullstatus-on-load yes;
show-failedconnects yes;
except-hosts {
"*@203.219.73.176";
"*@77.*";
"*@79.*";
"*Shqipet@*";
"*Zemra@*";
};
};
};

link Services.Zemra.Org {
username *;
hostname 72.20.42.110;
bind-ip *;
port 3366;
hub *;
password-connect "Services";
password-receive "Services";
class servers;
options {
};
};
link Stats.Zemra.Org {
username *;
hostname 72.20.42.110;
bind-ip *;
port 3366;
hub *;
password-connect "Links";
password-receive "Links";
class servers;
options {
};
};

ulines {
Services.Zemra.Org;
Stats.Zemra.Org;
};

drpass {
restart "RestartBaby";
die "DieMama";
};

log "ircd.log" {
/* Delete the log file and start a new one when it reaches 2MB, leave this out to always use the
same log */
maxsize 2097152;
flags {
oper;
kline;
connects;
server-connects;
kills;
errors;
sadmin-commands;
chg-commands;
oper-override;
spamfilter;
};
};

// This points the command /nickserv to the user NickServ who is connected to the set::services-server server
/*alias NickServ {
target "NickServ";
type services;
};*/

// If you want the command to point to the same nick as the command, you can leave the nick entry out
//alias ChanServ { type services; };

// Points the /statserv command to the user StatServ on the set::stats-server server
//alias StatServ { type stats; };

// Points the /superbot command to the user SuperBot
//alias SuperBot { type normal; };

/* Standard aliases */
alias nickserv { type services; };
alias ns { nick nickserv; type services; };
alias chanserv { type services; };
alias cs { nick chanserv; type services; };
alias memoserv { type services; };
alias ms { nick memoserv; type services; };
alias operserv { type services; };
alias os { nick operserv; type services; };
alias helpserv { type services; };
alias hs { nick helpserv; type services; };
alias irciihelp { type services; };
alias statserv { type services; };
alias ss { nick statserv; type services; };
alias botserv { type services; };
alias bs { nick botserv; type services; };
alias NickServ { type services; };
alias ChanServ { type services; };
alias OperServ { type services; };
alias HelpServ { type services; };
alias StatServ { type stats; };

alias "identify" {
format "^#" {
target "chanserv";
type services;
parameters "IDENTIFY %1-";
};
format "^[^#]" {
target "nickserv";
type services;
parameters "IDENTIFY %1-";
};
type command;
};

/* Standard aliases */
alias "services" {
format "^#" {
target "chanserv";
type services;
parameters "%1-";
};
format "^[^#]" {
target "nickserv";
type services;
parameters "%1-";
};
type command;
};

alias "identify" {
format "^#" {
target "chanserv";
type services;
parameters "IDENTIFY %1-";
};
format "^[^#]" {
target "nickserv";
type services;
parameters "IDENTIFY %1-";
};
type command;
};

/* This is an example of a real command alias */
/* This maps /GLINEBOT to /GLINE <parameter> 2d etc... */
alias "glinebot" {
format ".+" {
command "gline";
type real;
parameters "%1 +0 4Bots are not allowed in this server - 12Gline@Zemra.Org ";
};
type command;
};

tld {
mask *@*;
motd "ircd.motd";
rules "ircd.rules";
opermotd "ircd.opermotd";
};
ban nick {
mask "*Serv*";
reason "Reserved for Services";
};
ban ip {
mask 195.86.232.81;
reason "Delinked server";
};
ban server {
mask eris.berkeley.edu;
reason "Get out of here.";
};
ban user {
mask *tirc@*.saturn.bbn.com;
reason "Idiot";
};
ban realname {
mask "www.AlbaTok.com";
reason "Ndro Relaname";
};
ban realname {
mask "WwW.Tivendos.Net";
reason "Ndro Relaname";
};
except ban {
/* don't ban stskeeps */
mask *!*Zemra*@*;
};

deny dcc { filename "*sub7*"; reason "DCC Trojan..."; };
deny dcc { filename "*vbs*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };
deny dcc { filename "*bat*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };
deny dcc { filename "*com*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };
deny dcc { filename "*exe*"; reason "virus/trojan i mundshem, dcc nuk lejohet."; };

vhost {
vhost Operator.Zemra.Org;
from {
userhost *@*;
};
login operator;
password zemra;
};
vhost {
vhost Operatore.Zemra.Org;
from {
userhost *@*;
};
login operatore;
password zemra;
};

/* You can include other configuration files */
/* include "klines.conf"; */

/* Network configuration */
set {
network-name "Zemra";
default-server "Irc.Zemra.Org";
services-server "services.Zemra.Org";
stats-server "stats.zemra.Org";
help-channel "#Ndihme";
hiddenhost-prefix "Zemra";
prefix-quit " 12Vizitor nga 4«« ¤ 12www.Zemra.Org 4 ¤ »» ";
/* Cloak keys should be the same at all servers on the network.
* They are used for generating masked hosts and should be kept secret.
* The keys should be 3 random strings of 5-100 characters
* (10-20 chars is just fine) and must consist of lowcase (a-z),
* upcase (A-Z) and digits (0-9) [see first key example].
*/
cloak-keys {
"LCdRdwzb88hPkMmnGF3cbOv0b";
"mFFQaKFSjSl267cmmElq2uHqx";
"wHmk7pJULg8OuhCLfp74MgQId";
};

/* on-oper host */
hosts {
local "IRCop.Zemra.Org";
global "IRCop.Zemra.Org";
coadmin "Co-Admin.Zemra.Org";
admin "Admin.Zemra.Org";
servicesadmin "Services-Admin.Zemra.Org";
netadmin "NetAdmin.Zemra.Org";
host-on-oper-up "yes";
};
};

/* Server specific configuration */

set {
kline-address "GLine@Zemra.Org";
modes-on-connect "+icxvw";
auto-join "#ALbaChat";
modes-on-join "+ntrVCTfj 3:1 [5j#R1,7m#M5,2n#N1,7t#b]:3";
modes-on-oper "+Wxwgspq";
restrict-usermodes "icvwx";
snomask-on-oper "+cFfkejvGnNqsSo";
oper-auto-join "#ALbaChat,#Ndihme,#Ops,#Staff";
dns {
nameserver 127.0.0.1;
timeout 2s;
retries 2;
};
options {
hide-ulines;
/* You can enable ident checking here if you want */
identd-check;
flat-map;
allow-part-if-shunned;
fail-oper-warn;
show-connect-info;
};

maxchannelsperuser 15;

anti-spam-quit-message-time 10s;

static-quit " 12Vizitor nga 4«« ¤ 12www.Zemra.Org 4 ¤ »» ";

static-part "Client Parted from 4«« ¤ 12www.Zemra.Org 4 ¤ »» ";

// flat-map "Nuk keni access te mjafueshëm për komandën /map";

// flat-links "Nuk keni access te mjafueshëm për komandën /links.";

oper-only-stats "*";

/* Throttling: this example sets a limit of 3 connection attempts per 60s (per host). */
throttle {
connections 3;
period 60s;
};

/* Anti flood protection */
anti-flood {
nick-flood 2:60; /* 3 nickchanges per 60 seconds (the default) */
};

/* Spam filter */
spamfilter {
ban-time 1d; /* default duration of a *line ban set by spamfilter */
ban-reason "Spam/Advertising"; /* default reason */
virus-help-channel "#Ndihme"; /* channel to use for 'viruschan' action */
/* except "#Ndihme"; channel to exempt from filtering */
};
};

hideserver
{
disable-map yes;
disable-links yes;
map-deny-message "*** /Map Nuk keni autorizim për këtë komandë";
links-deny-message "*** /Links Nuk keni autorizim për këtë komandë";
hide
{
services.zemra.org;
stats.zemra.org;
};
};
/*
* Unrealircd.conf by DeviL (Info@Zemra.Org).
* For any help visite http://www.Zemra.Org
*/

Anope Services

2011-09-23T20:58:00.001-07:00

How To Install Anope IRC Services

wget http://ircd.zemra.org/anope/services/anope-1.8.9.tar.gz
tar xfz anope-1.8.9.tar.gz
cd anope-1.8.9
./Config
make or gmake
make install
cd ..
cd services
cp example.conf services.conf
./services

services.conf



###########################################################################

#    Anope IRC Services config file by DeviL

#    http://www.Zemra.Org - info@zemra.org

#

#              IRCD configuration

#

###########################################################################

IRCDModule "unreal32"

EncModule "enc_none"

###########################################################################
#
# Core module configuration
#
###########################################################################

HostCoreModules "hs_help hs_on hs_off hs_group hs_list hs_set hs_setall hs_del hs_delall"

MemoCoreModules "ms_send ms_cancel ms_list ms_read ms_del ms_set ms_info ms_rsend ms_check ms_staff ms_sendall ms_help"

HelpCoreModules "he_help"

BotCoreModules "bs_help bs_botlist bs_assign bs_set bs_kick bs_badwords bs_act bs_info bs_say bs_unassign bs_bot bs_fantasy bs_fantasy_kick bs_fantasy_kickban bs_fantasy_owner bs_fantasy_seen bs_fantasy_unban"

OperCoreModules "os_raw os_help os_global os_stats os_oper os_admin os_staff os_mode os_kick os_clearmodes os_killclones os_akill os_sgline os_sqline os_szline os_chanlist os_userlist os_logonnews os_randomnews os_opernews os_session os_noop os_jupe os_ignore os_set os_reload os_update os_restart os_quit os_shutdown os_defcon os_chankill os_svsnick os_oline os_umode os_modload os_modunload os_modlist os_modinfo"

NickCoreModules "ns_help ns_register ns_group ns_identify ns_access ns_set ns_drop ns_recover ns_release ns_sendpass ns_ghost ns_alist ns_info ns_list ns_logout ns_status ns_update ns_getpass ns_getemail ns_forbid ns_suspend"

ChanCoreModules "cs_help cs_register cs_identify cs_set cs_xop cs_access cs_akick cs_drop cs_sendpass cs_ban cs_clear cs_modes cs_getkey cs_invite cs_kick cs_list cs_logout cs_topic cs_info cs_getpass cs_forbid cs_suspend cs_status"
###########################################################################
#
# Remote server configuration
#
###########################################################################

RemoteServer 100.99.98.97 1234 "password"
#RemoteServer2 localhost 6667 "mypass"
#RemoteServer3 localhost 6667 "mypass"

LocalAddress 100.99.98.97 1234

###########################################################################
#
# Services identification and pseudoclient names
#
###########################################################################

# ServerName [REQUIRED]
# Specifies the IRC server name which Services should use. May be
# overridden by the -name command-line option.

ServerName "Sherbimet.Zemra.Org"

# ServerDesc [REQUIRED]
# Specifies the text which should appear as the server's information in
# /whois and similar queries. May be overridden by the -desc
# command-line option.

ServerDesc "Sherbimet për Zemra.Org"

# ServiceUser [REQUIRED]
# Specifies the user@host mask which should be used by the Services
# pseudoclients. May be overridden by the -user and -host command-line
# options.

ServiceUser "Sherbimet@Zemra.Org"

# ...Name [REQUIRED except as noted below]
# Specify the nicknames (first parameter) and "real" names (second
# parameter) for the Services pseudoclients. BotServ and DevNull may
# be disabled by commenting out the appropriate lines below. Disabling
# BotServ is recommended on large networks.

NickServName "NickServ" "Nickname Server"
ChanServName "ChanServ" "Channel Server"
MemoServName "MemoServ" "Memo Server"
BotServName "BotServ" "Bot Server"
HelpServName "HelpServ" "Help Server"
OperServName "OperServ" "Operator Server"
GlobalName "Global" "Global Noticer"
DevNullName "DevNull" "/dev/null -- message sink"
HostServName "HostServ" "vHost Server"

# ...Alias [OPTIONAL]
# Specify alternate nicknames for services. When a user will /msg
# NickServAlias something, it will be forwarded to NickServName, and
# NickServName will answer. This can be used to ease the migration
# from another network, for example if your services are called
# NickKeeper, ChanKeeper, etc ... and the other network calls them
# NickServ, ChanServ, etc ...

#NickServAlias "NickServ2" "Nickname Server Forwarder"
#ChanServAlias "ChanServ2" "Channel Server Forwarder"
#MemoServAlias "MemoServ2" "Memo Server Forwarder"
#BotServAlias "BotServ2" "Bot Server Forwarder"
#HelpServAlias "HelpServ2" "Help Server Forwarder"
#OperServAlias "OperServ2" "Operator Server Forwarder"
#GlobalAlias "Global2" "Global Noticer Forwarder"
#DevNullName "DevNull2" "/dev/null -- message sink Forwarder"
#HostServAlias "HostServ2" "vHost Server Forwarder"

###########################################################################
#
# Services data filenames
#
###########################################################################

# NOTE: All filenames are relative to the Services data directory.

# PIDFile [REQUIRED]
# Specifies the name of the file containing Services' process ID.

PIDFile services.pid

# MOTDFile [REQUIRED]
# Specifies the name of the Message of the Day file.

MOTDFile services.motd

# ...DB [REQUIRED]
# Specifies the filenames for the various Services subsystems' databases.

NickServDB nick.db
#PreNickServDB prenick.db
ChanServDB chan.db
BotServDB bot.db
OperServDB oper.db
NewsDB news.db
ExceptionDB exception.db
HostServDB hosts.db

# There is no more databases for AKILLs. This setting is kept to allow
# you to import old AKILL database, and is optional. (If not given,
# Services will look for a file named akill.db.)

# AutokillDB akill.db

###########################################################################
#
# Network information
#
###########################################################################

# HelpChannel [OPTIONAL]
#
# When defined, every users that has or gets op status on this channel
# automatically receive the +h user mode.

HelpChannel "#Ndihme"

# LogChannel [OPTIONAL]
#
# When defined, services will output log messages to this channel.
# IMPORTANT: This can be a security risk so make certain this channel
# is sufficiently protected from normal access.

LogChannel "#Staff"

# LogBot [OPTIONAL]
#
# When defined, services will output all BotServ chatter to the defined
# LogChan above. It shows all uses of BotServ ACT and SAY commands. Note
# that there is no logging to the log file. Only works if LogChannel is
# also defined.

LogBot

# NetworkName [REQUIRED]
#
# This is the name of the network the Services are running on.

NetworkName "Zemra"

# Numeric [OPTIONAL]
# Many ircd identify themselves with a Numeric ID when using this option
# consult your ircds documentation before using this
#Numeric "3AX"
Numeric "250"

###########################################################################
#
# Basic functionality
#
###########################################################################

# UserKey1|2|3 [REQUIRED]
#
# These keys are required to initiate the random number generator. These
# numbers MUST be random as you want your passcodes to be random. Don't
# give these keys to anyone! Keep them private!
# For those pple who don't understand what to do here: Just pick three
# _different_ _random_ numbers with about 6 or 7 digits and put them here.
# If the keys don't work, they might be too long or you forgot to remove
# the # in front of them. Example:
# UserKey1 9866235

UserKey1 4465231
UserKey2 1656466
UserKey3 7215454

# NoBackupOkay [DISCOURAGED]
# Allows Services to continue file write operations (i.e. database
# saving) even if the original file cannot be backed up. Enabling this
# option may allow Services to continue operation under some conditions
# when it might otherwise fail, such as a nearly-full disk.
#
# *** NOTE ***
# Enabling this option can cause irrecoverable data loss under some
# conditions, so make CERTAIN you know what you're doing when you
# enable it!

#NoBackupOkay

# StrictPasswords [RECOMMENDED]
# When enabled, causes Services to perform more stringent checks on
# passwords. If this is disabled, Services will only disallow a
# password if it is the same as the entity (nickname or channel name)
# with which it is associated. When enabled, however, Services will
# also check that the password is at least five characters long, and
# in the future will probably check other things as well.

StrictPasswords

# BadPassLimit [RECOMMENDED]
# Sets the number of invalid password tries before Services removes a
# user from the network. If a user enters invalid passwords
# for any Services function or combination of functions during a
# single IRC session (subject to BadPassTimeout, below), Services will
# issue a /KILL for the user. If not given, Services will ignore
# failed password attempts (though they will be logged in any case).

BadPassLimit 3

# BadPassTimeout [OPTIONAL]
# Sets the time after which invalid passwords are forgotten about. If
# a user does not enter any incorrect passwords in this amount of time,
# the incorrect password count will reset to zero. If not given, the
# timeout will be disabled, and the incorrect password count will never
# be reset until the user disconnects.

BadPassTimeout 1h

# UpdateTimeout [REQUIRED]
# Sets the delay between automatic database updates. This timer is
# reset by the OperServ UPDATE command.

UpdateTimeout 5m

# ExpireTimeout [REQUIRED]
# Sets the delay between checks for expired nicknames and channels.
# The OperServ UPDATE command will also cause a check for expiration
# and reset this timer.

ExpireTimeout 30m

# ReadTimeout [REQUIRED]
# Sets the timeout period for reading from the network.

ReadTimeout 5s

# WarningTimeout [REQUIRED]
# Sets the interval between sending warning messages for program
# errors via WALLOPS/GLOBOPS.

WarningTimeout 4h

# TimeoutCheck [REQUIRED]
# Sets the (maximum) frequency at which the timeout list is checked.
# This, combined with ReadTimeout above, determine how accurately timed
# events, such as nick kills, occur; it also determines how much CPU
# time Services will use doing this. Higher values will cause less
# accurate timing but less CPU usage.
#
# This shouldn't be set any higher than 10 seconds, and 1 second is
# best if your system is powerful enough (or your network small enough)
# to handle it. 0 will cause the timeout list to be checked every time
# through the main loop, which will probably slow down Services too
# much to be useful on most networks.
#
# Note that this value is not an absolute limit on the period between
# checks of the timeout list; the period may be as great as ReadTimeout
# (above) during periods of inactivity.

TimeoutCheck 3s

# KeepLogs [RECOMMENDED]
#
# Sets the number of days log files are kept. If you don't give it, or if
# you set it to 0, logs will be kept indefinitely.
#
# NOTE: Services must run 24 hours a day for this feature to work.

KeepLogs 7

# KeepBackups [RECOMMENDED]
#
# Sets the number of days backups of databases are kept. If you don't give
# it, or if you set it to 0, Services won't backup the databases.
#
# NOTE: Services must run 24 hours a day for this feature to work.

KeepBackups 3

# ForceForbidReason [OPTIONAL]
#
# If set, Services will require a reason when a forbid is added, else
# the reason is optional. This directive also applies to SUSPENDed
# channels as well.

ForceForbidReason

# UsePrivmsg [OPTIONAL]
#
# This directive will make Services send PRIVMSGs to users instead of
# NOTICEs by default, and allow users to set how Services should
# communicate with them.
#
# This is a feature that is against the IRC RFC and should be used
# _only_ if absolutely necessary.

#UsePrivmsg

# DumpCore [OPTIONAL]
#
# Setting this directive will make Anope dump core when a segmentation
# fault occurs. This is generally not needed, but if Anope is crashing
# on your network and you want to make a bug report, having a core
# file may be of great help.

#DumpCore

# LogUsers [OPTIONAL]
#
# Defines whether Anope will log user connections, disconnections and
# nickname changes. You may have to do so in case you ever need to
# transmit user information to your local authorities.

#LogUsers

# HideStatsO [OPTIONAL]
#
# Setting this directive will make Services only show Stats o to
# IRC Operators.

HideStatsO

# GlobalOnCycle [OPTIONAL]
#
# Setting this directive will make Services send global messages on
# starting up and shutting down/restarting.

GlobalOnCycle

# GlobalOnCycleMessage [REQUIRED if GlobalOnCycle is specified]
# This is the global message sent when the Services are
# being shutdown/restarted if using GlobalOnCycle
GlobalOnCycleMessage "Servicet restartohen, së shpejti do të kthehen online"

# GlobalOnCycleUP [OPTIONAL]
# If defined this message will be sent global when the services join
# the network.
GlobalOnCycleUP "Servicet u kthyen online përsëri - çaste të bukura"

# AnonymousGlobal [OPTIONAL]
# hides the oper's nick in a global message/notice
#AnonymousGlobal

# NickRegDelay [OPTIONAL]
# Prevents users from regging their nick if they are not
# connected for at least X seconds.
NickRegDelay 120

# UseSVSHOLD [OPTIONAL]
# Allows Bahamut-networks to use SVSHOLD instead of the services
# enforcer. This option has been introduced in Bahamut 1.4.35 and
# places a temporary Q:Line instead of introducing a new nick,
# which is better for both CPU and bandwidth. If you enable this
# option on a pre-1.4.35 Bahamut, it is most likely to break.
# This option now works with Unreal 3.2
#UseSVSHOLD

# RestrictOperNick [OPTIONAL]
# Forbids the registration of nicks that contain nick with services
# access. So if Tester is a Services Oper, for example, You can't
# register NewTester or Tester123 unless you are an IRC operator.
# IMPORTANT: Remember that you have to be an ircop if you want to
# register the root's nick when setting up Anope for the
# the first time.
# RestrictOperNicks

# UseTokens [OPTIONAL]
# Allows irc networks to use TOKEN commands instead of the
# standard commands. This saves bandwidth but can break older
# modules that are not set to trap for TOKEN - if you are using
# older modules do NOT use this option
#UseTokens

# UseSVS2MODE [OPTIONAL]
# On Unreal IRCD use SVS2MODE instead of SVSMODE, doing this will
# show services changing user modes.
#UseSVS2MODE

# NewsCount [OPTIONAL]
# The number of LOGON/OPER News item to display when a user logs
# on. The default value is 3
#NewsCount 3

# UnRestrictSAdmin [OPTIONAL]
# On many ircd Anope removes the umode of +a from users whom are not
# Service Admin in Anope. This mode is NOT used by Anope for any form
# of access. Thus this option allows them to keep the mode without having
# to be a Service Admin in Anope
#UnRestrictSAdmin

# UlineServers [OPTIONAL]
#
# A list of ulined servers on your network, these servers are assumed they
# can set channel modes and we will not attempt to take them from them
# WARNING: do not put your user servers in this option

UlineServers "stats.Zemra.Org services.Zemra.Org"

# UseTS6 [OPTIONAL]
#
# Modern hybrid ircd like Ratbox 2.0.x support a protocol called TS6.
# However this protocol is optional thus our default support is for without
# TS6, if you want to take advantage of TS6, enable this option.

#UseTS6

###########################################################################
#
# Mail-related options
#
###########################################################################

# NOTE: if UseMail is not set, all parameters after it in this section
# are optional.

# UseMail [OPTIONAL]
#
# This option enables the mail commands in Services. You may choose
# to disable it if you have no sendmail-compatible mailer installed.

UseMail

# SendMailPath
[REQUIRED]
#
# This is how we should call SendMail to send a mail. It must be
# called with all parameters needed to make it scan the mail input
# to find the mail recipient; consult your SendMail documentation.
#
# Postfix users must use the compatible sendmail utility provided
# with it; this one needs no parameters on the command line.

SendMailPath "/usr/sbin/sendmail -t"

# SendFrom [REQUIRED]
#
# This is the e-mail from which all the e-mails are to be sent. It should
# really exist.

SendFrom services@Zemra.Org

# RestrictMail [OPTIONAL]
#
# When enabled, SENDPASS will be restricted to IRC operators.
#
# WARNING: if you choose to not enable this option, you should limit
# the number of processes the services user can have at a time (you can
# create a special user for this; remember to never launch Services as root).

RestrictMail

# MailDelay [RECOMMENDED]
#
# This controls the minimum amount of time an user must wait before sending
# another mail after it has sent one. It also controls the minimum time
# an user must wait before it can receive another mail.
#
# This feature prevents users from being mail bombed using Services and
# should definitely be used.

MailDelay 5m

# DontQuoteAddresses [OPTIONAL]
#
# When enabled, services will not attempt to "" the TO: fields in mails
#
# So far we only know of ESMTP/QMail which need this set.
#

#DontQuoteAddresses

###########################################################################
#
# NickServ configuration
#
###########################################################################

# NSForceEmail [RECOMMENDED]
# This option forces the users to give an e-mail when they register
# a nickname. If you have nicks in the database that have no e-mail
# set, they will be asked to set an e-mail when they identify their
# nickname until they set one. Also, this option prevents user from
# unsetting the password.
#
# This option is useful to resolve "lost password" problems.

NSForceEmail

# NSEmailReg [OPTIONAL]
# This option splits the nick registration into 2 steps, the first
# after registering a email with a passcode is sent to the supplied
# email address, this passcode needs to be entered with a confirm
# command before the nick registration will be completed.
#
# You must have mail / forcemail set for this to work correctly.
# It is also recommended that MailDelay be set to a sensible value
# to prevent mail flooding

# NSEmailReg

# NSDef... [OPTIONAL]
# Sets the default options for newly registered nicks. Note that
# changing these options will have no effect on nicks which are already
# registered.
#
# If both NSDefKill and NSDefKillQuick are given, the latter takes
# precedence. KILL IMMED cannot be specified as a default.
#
# Note: Both NSDefKill and NSDefKillQuick must be specified for Quick to take effect.
#
# NOTE: If you do not enable any of these options, a default of
# Secure, MemoSignon, and MemoReceive will be used, for backward
# compatibility. If you really want no options enabled by default, use
# NSDefNone.

#NSDefNone

#NSDefKill
#NSDefKillQuick
NSDefSecure
NSDefPrivate
NSDefHideEmail
NSDefHideUsermask
#NSDefHideQuit
#NSDefMsg
NSDefMemoSignon
NSDefMemoReceive

# NSDefLanguage [REQUIRED]
# Sets the default language non- and newly-registered will receive
# services' messages in. The numbers are the same as those
# used for the /nickserv SET LANGUAGE command, so look the at the help
# of this command for the list of currently supported languages.
#
# If you ever wanted to know how to translate services in your
# language, read the chapter about it in the README.

NSDefLanguage 1

# NSRegDelay [RECOMMENDED]
# Sets the minimum length of time between consecutive uses of the
# REGISTER command. If not given, this restriction is disabled (note
# that this allows "registration flooding").

NSRegDelay 30s

# NSExpire [RECOMMENDED]
# Sets the length of time before a nick registration expires.

NSExpire 90d

# NSRExpire [OPTIONAL]
# Sets the length of time a user gets to enter the confirmation code
# which has been e-mailed to them before the nick will be released
# for general use again

# NSRExpire 1d

# NSMaxAliases [RECOMMENDED]
# Sets the maximum number of nicks allowed in a group. If you
# set it to 0, or don't set it at all, no limits will be applied.

NSMaxAliases 16

# NSAccessMax [REQUIRED]
# Sets the maximum number of entries allowed on a nickname access list.

NSAccessMax 32

# NSEnforcerUser [@] [REQUIRED]
# Sets the username (and possibly hostname) used for the fake user
# created when NickServ collides a user. Should be in user@host
# format. If the host is not given, the one from ServicesUser is
# used.

NSEnforcerUser enforcer@Zemra.Org
#NSEnforcerUser enforcer

# NSReleaseTimeout [REQUIRED]
# Sets the delay before a NickServ-collided nick is released.

NSReleaseTimeout 1m

# NSAllowKillImmed [OPTIONAL]
# When enabled, allows the use of the IMMED option with the NickServ
# SET KILL command.

#NSAllowKillImmed

# NSNoGroupChange [OPTIONAL]
# When enabled, the NickServ GROUP command won't allow any group change.
# This is recommended for better performances and to protect against
# nick stealing, however users will have less flexibility.

#NSNoGroupChange

# NSListOpersOnly [OPTIONAL]
# When enabled, limits use of the NickServ LIST command to IRC
# operators.

NSListOpersOnly

# NSListMax [REQUIRED]
# Specifies the maximum number of nicks to be returned for a NickServ
# LIST command.

NSListMax 50

# NSGuestNickPrefix [REQUIRED]
# When a user's nick is forcibly changed to enforce a "nick kill", their
# new nick will start with this value. The rest will be made up of 6 or 7
# digits.

NSGuestNickPrefix "Guest"

# NSSecureAdmins [RECOMMENDED]
# When enabled, prevents the use of the DROP, FORBID, GETPASS, and
# SET PASSWORD commands by Services admins on other Services admins or
# the Services root(s).

NSSecureAdmins

# NSStrictPrivileges [RECOMMENDED]
#
# When enabled, any user wanting to use the privileges of Services Root, Services
# Admin or Services Operator must have been logged as an IRC Operator with the
# /oper command.

NSStrictPrivileges

# NSModeOnID [OPTIONAL]
#
# When enabled, services will set the channel modes a user has access to upon
# identifying, assuming they are not already set.
#

# NSModeOnID

# NSRestrictGetPass [OPTIONAL]
#
# When enabled, services will only allow Services Root to use the getpass
# command on a nick.

NSRestrictGetPass

# NSNickTracking [OPTIONAL]
#
# When enabled, services will track your last nick identified when issuing
# nick changes.

NSNickTracking

# NSAddAccessOnReg [OPTIONAL]
#
# When enabled, services will add the usermask of registering users to the
# access list of their newly created account. If you disable this, users
# will always have to identify to nickserv before being recognized, unless
# they manually add an address to the access list of their account.

NSAddAccessOnReg

###########################################################################
#
# ChanServ configuration
#
###########################################################################

# CSDef... [OPTIONAL]
# Sets the default options for newly registered channels. Note that
# changing these options will have no effect on channels which are
# already registered.
#
# NOTE: If you do not enable any of these options, a default of
# KeepTopic, Secure, SecureFounder and SignKick will be used, for
# backward compatibility. If you really want no options enabled by
# default, use CSDefNone.

#CSDefNone

CSDefKeepTopic
CSDefOpNotice
CSDefPeace
#CSDefPrivate
#CSDefRestricted
CSDefSecure
#CSDefSecureOps
CSDefSecureFounder
CSDefSignKick
#CSDefSignKickLevel
#CSDefTopicLock
CSDefXOP

# CSMaxReg [RECOMMENDED]
# Limits the number of channels which may be registered to a single
# nickname.

CSMaxReg 10

# CSExpire [RECOMMENDED]
# Sets the number of days before a channel expires.

CSExpire 500d

# CSDefBantype [REQUIRED]
#
# Sets the default ban type for newly registered channels (and when
# importing old databases).
#
# bantype can be:
#
# 0: ban in the form *!user@host
# 1: ban in the form *!*user@host
# 2: ban in the form *!*@host
# 3: ban in the form *!*user@*.domain

CSDefBantype 2

# CSAccessMax [REQUIRED]
# Sets the maximum number of entries on a channel's access list.
# Channel access lists may contain only registered nicknames;
# therefore, checking each entry on the list requires only a single
# scaler comparison instead of a wildcard match, and this limit may be
# safely set much higher than (for example) the nickname access list
# size limit without impacting performance significantly.

CSAccessMax 1024

# CSAutokickMax [REQUIRED]
# Sets the maximum number of entries on a channel's autokick list.

CSAutokickMax 100

# CSAutokickReason [REQUIRED]
# Sets the default reason for an autokick if none is given.

CSAutokickReason "User has been banned from the channel"

# CSInhabit [REQUIRED]
# Sets the length of time ChanServ stays in a channel after kicking a
# user from a channel s/he is not permitted to be in. This only occurs
# when the user is the only one in the channel.

CSInhabit 15s

# CSListOpersOnly [OPTIONAL]
# When enabled, limits use of the ChanServ LIST command to IRC
# operators.

CSListOpersOnly

# CSListMax [REQUIRED]
# Specifies the maximum number of channels to be returned for a
# ChanServ LIST command.

CSListMax 50

# CSRestrictGetPass [OPTIONAL]
#
# When enabled, services will only allow Services Root to use the getpass
# command on a channel.

CSRestrictGetPass

# CSOpersOnly [OPTIONAL]
# If this is defined, only IRC Operators will be permitted to use ChanServ.

#CSOpersOnly

###########################################################################
#
# MemoServ configuration
#
###########################################################################

# MSMaxMemos [RECOMMENDED]
# Sets the maximum number of memos a user is allowed to keep by
# default. Normal users may set the limit anywhere between zero and
# this value; Services admins can change it to any value or disable it.
# If not given, the limit is disabled by default, and normal users can
# set any limit they want.

MSMaxMemos 20

# MSSendDelay [RECOMMENDED]
# Sets the delay between consecutive uses of the MemoServ SEND command.
# This can help prevent spam as well as denial-of-service attacks from
# sending large numbers of memos and filling up disk space (and
# memory). A 3-second wait means a maximum average of 150 bytes of
# memo per second per user under the current IRC protocol.

MSSendDelay 3s

# MSNotifyAll [OPTIONAL]
# Should we notify all appropriate users of a new memo? This applies
# in cases where a memo is sent to a nick which is in the group of
# another nick. Note that, unlike before, it is currently often more
# efficient to enable this.

MSNotifyAll

# MSMemoReceipt [OPTIONAL]
# Allow the use of memo receipts for the following groups:
# 1 - Opers Only
# 2 - Everybody
#
#MSMemoReceipt 1

###########################################################################
#
# BotServ configuration
#
###########################################################################

# BSDef... [OPTIONAL]
# Sets the default options for newly registered channels. Note that
# changing these options will have no effect on channels which are
# already registered.

BSDefDontKickOps
BSDefDontKickVoices
BSDefGreet
BSDefFantasy
BSDefSymbiosis

# BSMinUsers [REQUIRED]
# Minimum number of users there must be in a channel before the
# bot joins it. The best value for this setting is 1 or 2. This
# cannot be 0, otherwise topic retention and mode lock and such
# other things won't work.

BSMinUsers 1

# BSBadWordsMax [REQUIRED]
# Maximum number of entries a single bad words list can have.
# Setting it too high can reduce performances slightly.

BSBadWordsMax 32

# BSKeepData [REQUIRED]
# Amount of time data for a user that is used by BotServ is
# valid. If the data exceeds this time, it is reset or deleted
# depending the case. Do not set it too high otherwise your resources
# will be slightly affected.

BSKeepData 10m

# BSSmartJoin [OPTIONAL]
# The bot is currently not affected by any modes or bans when he
# tries to join a channel. But some people may want to make it
# act like a real bot, that is, for example, remove all bans
# that affect the bot before joining the channel, remove a
# ban that affects the bot set by an user when it is on the
# channel, and so on. Since it consumes a bit more CPU time,
# you should not comment it out on larger networks.

# BSSmartJoin

# BSGentleBWReason [OPTIONAL]
# This option will make the bot use a kick reason that does not retake
# the word when it is kicking the bot. This is especially useful if
# you have young people on your network.

BSGentleBWReason

# BSCaseSensitive [OPTIONAL]
# This option will make botserv use cAsE sEnSiTiVe checking for badwords

# BSCaseSensitive

###########################################################################
#
# HostServ configuration
#
###########################################################################

# HostSetters [DISCOURAGED]
# Specifies the nicks of NON-OPERS allowed to Set/Remove vHosts using
# HostServ. Can be re-loaded with /msg operserv reload
# You can specify more than one nick by separating each one by a space.
#
# Make sure you insert the correct nick(s) here..

HostSetters "Calypso DeviL"

###########################################################################
#
# OperServ configuration
#
###########################################################################

# ServicesRoot [REQUIRED]
# Specifies the Services "super-users". The super-users, or "roots" as in
# Unix terminology, are the only users who can add or delete Services
# admins.
#
# You can specify more than one nick by separating each one by a space.
#
# This is commented out by default; make sure you insert the correct
# nick before uncommenting it.

ServicesRoot "Calypso DeviL"

# SuperAdmin [OPTIONAL]
# When enabled, Services admins will be able to use SuperAdmin [ON|OFF]
# which will temporarily grant them extra privileges, such as being a
# founder of _all_ channels, ability to adjust another users modes etc..

SuperAdmin

# LogMaxUsers [OPTIONAL]
# Causes Services to write a message to the log every time a new user
# maximum is set.

LogMaxUsers

# ...Expiry [REQUIRED]
# Sets the default expiry time for, respectively, AKILLs, SGLINEs,
# SQLINEs and SZLINEs.

AutoKillExpiry 30d
ChanKillExpiry 30d
SGLineExpiry 30d
SQLineExpiry 30d
SZLineExpiry 30d

# AkillOnAdd [OPTIONAL]
#
# When enabled, this option makes the services send an AKILL command
# immediately after it has been added with AKILL ADD. This eliminates
# the need of killing the users after the akill has been added.

AkillOnAdd

# KillOnSGline [OPTIONAL]
#
# When enabled, this option makes the services send an (SVS)KILL command
# immediately after SGLINE ADD. This eliminates the need of killing the
# users after the SGLINE has been added.

# KillOnSGline

# KillOnSQline [OPTIONAL]
#
# When enabled, this option makes the services send an (SVS)KILL command
# immediately after SQLINE ADD. This eliminates the need of killing the
# users after the SQLINE has been added.

KillOnSQline

# KillClonesAkillExpire [REQUIRED]
# Sets the expiry time for autokills added for hosts that have been
# killed using the KILLCLONES command.

KillClonesAkillExpire 30m

# DisableRaw [RECOMMENDED]
#
# Disables the highly destructive OperServ RAW command.

#DisableRaw

# WallOper [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS when a user becomes an IRC
# operator. Note that this can cause WALLOPS floods when Services
# first connects to the network.

#WallOper

# WallBadOS [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS if a non-IRC-operator tries
# to use OperServ.

#WallBadOS

# WallOS... [OPTIONAL]
# Cause Services to send a WALLOPS/GLOBOPS on use of each of the
# OperServ commands listed.

WallOSGlobal
WallOSMode
WallOSClearmodes
WallOSKick
WallOSAkill
WallOSSGLine
WallOSSQLine
WallOSSZLine
WallOSNoOp
WallOSJupe
#WallOSRaw

# Wall...Expire [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS whenever respectively
# an AKILL, an SGLINE, an SQLINE, an SZLINE and a session limit
# exception expires.

#WallAkillExpire
#WallSGLineExpire
#WallSQLineExpire
#WallSZLineExpire
#WallExceptionExpire

# WallGetpass [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS on use of the NickServ or
# ChanServ GETPASS command.

WallGetpass

# WallSetpass [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS whenever a Services admin
# sets a password for a nickname or channel (s)he does not normally have
# privileges to set.

WallSetpass

# WallForbid [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS on use of the NickServ or
# ChanServ FORBID command.

WallForbid

# WallDrop [OPTIONAL]
# Causes Services to send a WALLOPS/GLOBOPS whenever a Services admin
# drops a nickname or channel (s)he does not normally have
# privileges to drop.

WallDrop

# LimitSessions [OPTIONAL]
# Enables session limiting. Session limiting prevents users from
# connecting more than a certain number of times from the same host at the
# same time - thus preventing most types of cloning. Once a host reaches
# it's session limit, all clients attempting to connect from that host
# will be killed. Exceptions to the default session limit, which are based
# on host names, can be defined via the exception list. It should be noted
# that session limiting, along with a large exception list, can degrade
# services' performance. See the source and comments in sessions.c and the
# online help for more information about session limiting.
#
# Session limiting is meant to replace the CheckClones and KillClones
# code. It is therefore highly recommended that they are disabled when
# session limiting has been enabled.
#
# NOTE: This option is not available when STREAMLINED is defined in
# the Makefile.

LimitSessions

# DefSessionLimit
[REQUIRED]
# Default session limit per host. Once a host reaches it's session limit,
# all clients attempting to connect from that host will be killed. A value
# of zero means an unlimited session limit.

DefSessionLimit 70

# MaxSessionLimit
[REQUIRED]
# The maximum session limit that may be set for a host in an exception.

MaxSessionLimit 30

# ExceptionExpiry [REQUIRED]
# Sets the default expiry time for exceptions.

ExceptionExpiry 1d

# SessionLimitExceeded [OPTIONAL]
# The message that will be NOTICE'd to a user just before they are removed
# from the network because their's host session-limit has been exceeded.
# It may be used to give a slightly more descriptive reason for the
# impending kill as apposed to simply "Session limit exceeded". If this is
# commented out, nothing will be sent.

SessionLimitExceeded "The session limit for your host %s has been exceeded."

# SessionLimitDetailsLoc [OPTIONAL]
# Same as above, but should be used to provide a website address where
# users can find out more about session limits and how to go about
# applying for an exception. If this is commented out, nothing will be
# sent.
#
# This option has been intentionally commented out in an effort to remind
# you to change the URL it contains. It is recommended that you supply an
# address/url where people can get help regarding session limits.

SessionLimitDetailsLoc "Vizitoni http://zemra.org/forum/index.php?topic=988.msg1337#msg1337 per me teper info reth session limits."

# MaxSessionKill [OPTIONAL]
#
# If given and different from 0, this option tells the Services to add an
# AKILL when there is number subsequent kills for the same hostname, preventing
# the network from KILL flood.

MaxSessionKill 5

# SessionAutoKillExpiry [OPTIONAL]
#
# Sets the expiry time for autokills added for hosts that need to be
# AKILLed as controlled by the MaxSessionKill option.
#
# If not given, the default value is 30 minutes.

SessionAutoKillExpiry 30m

# CheckClones [DEPRECATED]
# Causes Services to try and detect "clones" connecting to the network.
# A WALLOPS (or GOPER, if supported on the IRC server) will be sent if
# Services thinks it has found clones.
#
# This feature has been superseded by Session Limiting.
#
# sets the minimum number of users which must successively
# connect to the network before Services will send a clone warning.
#
# sets the maximum time that can elapse between successive
# users before Services decides they are not clones.
#
# sets the minimum time between clone warnings for
# clones from the same host.
#
# NOTE: This option is not available when STREAMLINED is defined in
# the Makefile.

CheckClones 5 10s 30s

# KillClones [DISCOURAGED] [DEPRECATED]
# Causes Services to kill users which trigger the clone warnings. (If
# CheckClones is disabled, this will have no effect.)
#
# This feature has been superceded by Session Limiting.
#
# BEWARE! The clone checking code is easily fooled; it can be
# triggered falsely under many conditions, for example:
#
# - Multiple users connecting from a shell machine.
#
# - A single user repeatedly connecting and disconnecting.
#
# Be very sure you know what you're doing before you even think about
# enabling this option, and remember that Services comes with no
# warranty.
#
# If that wasn't enough discouragement:
#
# ***** DO NOT ENABLE THIS OPTION! *****
#
# NOTE: This option is not available when STREAMLINED is defined in
# the Makefile.

#KillClones

# AddAkiller [OPTIONAL]
# Adds the nickname of the Operator issuing an AKILL to the kill reason.
#
AddAkiller

# OSOpersOnly [RECOMMENDED]
# If this is defined, only IRC Operators will be permitted to use
# OperServ, regardless of module based command access restrictions.

OSOpersOnly

###########################################################################
#
# DefCon configuration
#
###########################################################################

# DefConLevel [OPTIONAL]
# Default defcon level (1-5) to use when starting services up, level 5
# instructs services to run as normal.

#DefConLevel 5

# DefCon1-4 [REQUIRED if Defcon is activated]
# These numercics determine which of the following operations take place
# at each level, the correct numeric can be found by adding together the
# number for each restriction you wish to place at a level.
# 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

#DefCon4 23
# No channel reg + No Nick Reg + No MLOCK changes + Use Reduced Session Limit
# 1 + 2 + 4 + 16

#DefCon3 31
# As DefCon4 + Services will Force Chan Mode's on channels
# 23 + 8

#DefCon2 159
# As DefCon3 + Services will silently ignore everyone but opers
# 31 + 128

#DefCon1 415
# As DefCon2 + AKILL all new clients trying to connect
# 159 + 256

# DefConSessionLimit
[REQUIRED if DefCon is activated]
# New session limit to use when a defcon level is using "reduced"
# session limiting.
# NOTE: When using DefCon this value needs to be defined
#DefConSessionLimit 2

# DefConAkillExpire [REQUIRED if DefCon is activated]
# Length of time to add the AKILL for when DEFCON is preventing
# all new clients from connecting to the network
#
# NOTE: As with all expire times, the expirey check will only be
# carried out once every "ExpireTimeout" so if this setting is
# 30m the the akill could last for 30m regardless of this setting.
#
# NOTE: When using DefCon this value needs to be defined
#DefConAkillExpire 5m

# DefConChanModes [REQUIRED if DefCon is activated]
# The channel modes to set on all channel's when the DefCon channel
# mode system is in use.
#
# NOTE: Choose these modes carefully, because when defcon switches to
# a level which does NOT have the mode setting selected, services will
# set the reverse on all channel's, e.g. if this setting is +RN
# when defcon is used all channel's will be set to +RN, when
# defcon is removed, channels will all be set to -RN. You don't
# want to set this to +k for example because when defcon is removed all
# channels will -k.
# NOTE: mlock'ed modes will not be lost
#DefConChanModes "+R"

# DefConTimeOut [OPTIONAL]
# This value can be used to automatically return the network to
# defcon 5 after the specified time period - just in case any opers
# forget to remove a defcon setting.
#DefConTimeOut 15m

# GlobalOnDefcon [OPTIONAL]
#
# Setting this directive will make Services send a global message on
# Defcon Level changes.
#GlobalOnDefcon

# GlobalOnDefconMore [OPTIONAL]
#
# Setting this directive will make Services send a global message on
# Defcon Level changes. Uncommenting this will allow you to send along
# with the new level, the DefconMessage.
#GlobalOnDefconMore

#DefconMessage "Put your message to send your users here. Dont forget to uncomment GlobalOnDefconMore"

# DefConOffMessage [OPTIONAL]
#
# If this is defined, it will be used in place of GlobalOnDefcon and
# GlobalOnDefconMore when defcon is returned to level 5
#DefConOffMessage "Serviset janë përsëri online - çaste të bukura"

# DefConAkillReason [REQUIRED if DefCon is activated]
#
# When using DEFCON this setting will be used when any clients are killed
# or akilled from the network by defcon
#
#DefConAkillReason "This network is currently not accepting connections, please try again later"

###########################################################################
#
# MySQL configuration
#
###########################################################################
#
# Mysql [OPTIONAL]
#
# Your MySQL configuration for use with Anope.
# To disable MySQL functionality, just comment out this block.
# To make use of MySQL use these directives and change their
# setting to the appropriate values.
#
# MysqlHost defines the Mysql server hostname.
# MysqlUser defines the Mysql user to log in with.
# MysqlPass defines the Mysql pass required for the specified user to log in.
# MysqlName defines the Mysql database name Anope uses
# MysqlSock defines the Mysql UNIX socket
# MysqlPort defines the Mysql TCP port
#
#MysqlHost "localhost"
#MysqlUser "Anonymous"
#MysqlPass ""
#MysqlName "anope"
#MysqlSock "/tmp/mysql.sock"
#MysqlPort 3306

# MysqlSecure "|||" [OPTIONAL]
#
# Method for storing passwords on MySQL. Available methods are:
# Empty or not set will save your passwords as clear text.
# des : Encrypt using a simple DES algorithm.
# md5 : Produces the md5 hash for the password.
# sha : Calculates the checksum using a Secure Hash Algorithm.
# key : Encodes using "key" as password.
# Please read docs/MYSQL file for more info and details.
#
#MysqlSecure ""

# MysqlRetries [OPTIONAL]
# MysqlRetryGap [OPTIONAL]
#
# These values let you define how often and with how much interruption Anope
# shall retry to open a connection when losing the contact to the mysql db.
# The product of these values must be between 1 and 60.
#
#MysqlRetries 10
#MysqlRetryGap 1

# UseRDB [OPTIONAL]
#
# Enable this if you want anope to load its data from a remote database.
# (e.g. MySQL)
#
#UseRDB

###########################################################################
#
# Module configuration
#
###########################################################################
#
# ModuleAutoload [OPTIONAL]
#
# When compiled with module support, this contains a space separated list
# of modules to automatically load as soon as possible, e.g. IRCD support modules.
#
ModuleAutoload "os_info os_clientjoin cs_enforce cs_appendtopic ns_noop"

# ModuleDelayedAutoload [OPTIONAL]
#
# When compiled with module support, this contains a space separated list
# of modules to automaticaly load when services are ready for new clients.
# e.g. new pesudo clients such as CatServ :-) *meow*
# By default a number of modules that we found worth adding by default are
# loaded. Feel free to change this if you want to add more, or remove some
# from the list.
#
ModuleDelayedAutoload "ns_maxemail ns_ajoin"

###########################################################################
#
# Module specific configuration
#
###########################################################################
#
# This section contains configuration options specific to certain modules.
# The options in here are for the modules shipped by default. You can add
# more options for other modules you load here. Check the documentation of
# the module to see what configuration options it provides.

# NSEmailMax [OPTIONAL]
# Module: ns_maxemail
#
# Limit the amount of registrations with the same email address to the
# amount given here. If set to 0 or left commented, there will be no limit
# enforced when registering new accounts or using /msg NickServ SET EMAIL.
#
#NSEmailMax 1

# NSAutoOPDBName [OPTIONAL]
# Module: ns_noop
#
# Use the given filename as database for the autoop list. If not given,
# the default of "autoop.db" will be used.
#
#NSAutoOPDBName "autoop.db"

# OSInfoDBName [OPTIONAL]
# Module: os_info
#
# Use the given filename as database for the oper information lines.
# If not given, the default of "os_info.db" will be used.
#
OSInfoDBName "os_info.db"
# BotNick [REQUIRED]
# Module: ircd_vhostserv
# Define what nick the bot will have.
#
BotNick "HostServ"

# BotIdent [REQUIRED]
# Define the bot identd.
#
BotIdent "Bot"

# BotHost [REQUIRED]
# Define the bot hostname or vhost.
#
BotHost "Zemra.Host.Bot"

# BotReal [REQUIRED]
# Define the bot realname.
#
BotReal "/msg vHostServ Help"

# vHostChannel [REQUIRED]
# Define your network vhost channel.
#
vHostChannel "#Ndihme"

# BanClearTime [REQUIRED]
# Sets the timeout period after which a particular ban set by
# the bot will be removed.
#
BanClearTime 5h

# BotModes [OPTIONAL]
# Define what modes the bot will have.
#
BotModes "+SqB"

# JoinLogChannel [OPTIONAL]
# Define this if you want the bot to automatically
# join services log channel.
#
JoinLogChannel

# RestrictHosts [RECOMMENDED]
# Define unallowed vhosts which will be match using
# wildcards. This is not case-sensitive.
#
RestrictHosts "*ircop* *admin* *root* *staff* *sex* *porn*"

# KickBanRestrictHosts [OPTIONAL]
# Define this to kick banned users who request
# restricted hosts. If this option is enabled
# RestrictHosts setting is required.
#
KickBanRestrictHosts

# End of config: ircd_vhostserv
# AJoinDB [OPTIONAL]
# Module: ns_ajoin
#
# Use the given filename as database to store the AJOINs.
# If not given, the default of "ns_ajoin.db" will be used.
#
AJoinDB "ns_ajoin.db"

# AJoinDefChans [OPTIONAL]
# Module: ns_ajoin
#
# Space seperated list of default ajoin channels.
# When a new nick is registered these will be automatically
# added to the users' AJOIN list.
#
AJoinDefChans "#ALbaChat"

# AJoinUnRegistered [OPTIONAL]
# Module: ns_ajoin
#
# When set ns_ajoin will AJOIN all connecting users
# who aren't using a registered nick (they don't need
# to be identified) to the default ajoin channels.
# Note that users will be unable to join channels with
# a key or invitemode set.
#
# Be aware the most users will experience this as very
# abusive and it will likely give your network a bad
# reputation.
# This was added only because under some circumstances
# it has a legit use.
#
#AJoinUnRegistered

*
**/

#include "module.h"

#EOF

NeoStats

2011-09-23T20:57:00.000-07:00

How To Install NeoStats

 1. wget http://shkarko.zemra.org/NeoStats-3.0.1.tar.gz

2. tar -xvf NeoStats-3.0.1.tar.gz

3. cd NeoStats-3.0.1

4. ./configure --help

./configure --enable-unreal32

5. ENTER

6. make

7. make install

8. cd

9. cd NeoStats3.0

10. ./bin/makeconf

What will your server name be? (ie: stats.zemra.org)
[stats.zemra.org] -> <--- stats.yourdomain.com What is your IRC server's IP? (ie: 127.0.0.1) [127.0.0.1] -> <--- Use IP That was given by your hosting. What is the IRCd's Link port? (ie: 7890) [6667] -> <--- Port that is opened on HUB Server for Servers\Links. What is the IRCd's Link password for stats? (ie: bleh) [LinkPass] -> <--- Password for connecting. ( C\N lines in IRCDs server). NeoStats Server comment? [NeoStats 2.5 IRC Statistical Server!] -> <--- Description of your NeoStats Server. Network name? (refer to your networks file. ie: ZemraOrg-IRC) [SomeNet-IRC] -> <--- Name of your Network. The host NeoStats is connecting from, most people use services.zemra.org [NeoStats.Net] -> <--- services.yourdomain.com NeoStats User? (This is the part before @yourhost.net) [Neo] -> <--- Ident for NeoStats. What channel should NeoStats join on IRC? [#services] -> <--- Channel that NeoStats will auto join on startup. Time in seconds we wait before attempting to reconnect to the server on a split? [10] -> <--- Time in seconds we wait before attempting to reconnect to the server on a split. What IP should NeoStats Bind to? (ie: 127.0.0.1) This is optional. See neostats.cfg for more information [127.0.0.1] -> <--- Use IP that was given by hosting.

12. pico neostats.conf



##################################################

## Configuration file for NeoStats

## Created: Fri, Dec 3 2010 - 09:55:26 UTC

## Web: http://www.Zemra.Org

## File Revision: 3.0

##################################################

##################################################
#Each of the options has an indicator as follows:
# [REQUIRED] - must be set or NeoStats will not run.
# [RECOMMENDED] - optional but may cause problems if not set.
# [OPTIONAL] - optional and the feature will be disabled if not set.
# [DISCOURAGED] - may cause undesirable side effects if enabled.
##################################################

#################################
# NeoStats Server Configuration #
#################################

ServerConfig {
# NAME = "" [REQUIRED]
# Specifies the name of the NeoStats Server as it will appear on
# the network. e.g.
#
# SERVER_NAME = "stats.neostats.net"
#
# When NeoStats links, it will appear as stats.neostats.net.
Name = "stats.zemra.org"

# INFO = "" [REQUIRED]
# Specify the description of the server that
# appears when you do /links e.g.
#
# INFO "Network Auxiliary Services"
Info = "NeoStats 3.0 IRC Services"

# SERVICECHANNEL="#" [REQUIRED]
# Specify the channel that all bots on NeoStats
# will automatically join, and echo out any
# important information e.g.
#
# SERVICECHANNEL="#services"
#
# Makes NeoStats, and all the other bots join #services channel on
# start-up/load.
ServiceChannel = "#services"

# SERVER_NUMERIC = [RECOMMENDED]
# Specify the numeric of the server to send on connect.
# This must be a value between 1 and 254, and must not be in use by
# any other IRC server on the network.
#
# SERVER_NUMERIC = 1
ServerNumeric = 1

# BINDTO = [OPTIONAL]
# Make NeoStats bind to a particular IP Address. If not
# specified NeoStats will attempt to find this address
# itself. e.g.
#
# BINDTO 203.203.123.12
#
# All outgoing connections from NeoStats will originate from this
# IP address
# This IP address should not be localhost (127.0.0.1)
BindTo = "72.20.42.110"

# PROTOCOL = "
" [REQUIRED]
# Specifies the protocol module to use.
# Valid protocol options are:
# unreal31 unreal32 ultimate2 ultimate3
# hybrid7 bahamut14 bahamut18 plexus
# ircup10 asuka nefarious
# client
#
# PROTOCOL = "unreal32"
#
Protocol = "unreal32"
}

#################################
# NeoStats Option Configuration #
#################################

Options {
# RECONNECTTIME = [RECOMMENDED]
# If NeoStats server gets split from the network, how long to wait
# before attempting to reconnect to the network. A value of 0 will
# cause NeoStats to shutdown and not attempt to reconnect. e.g.
#
# RECONNECTTIME = 10
#
# Specifies wait 10 seconds before trying to reconnect
#
# RECONNECT_TIME = 0
#
# Tells NeoStats to never reconnect to the network
#
# If not specified, NeoStats will default to 10 seconds.
ReconnectTime = 10

# USEPRIVMSG =
[DISCOURAGED]
# Specify if the bots should send all messages as privmsgs or as
# notices (Most Services use notice) e.g.
#
# USEPRIVMSG true
#
# If present or set to true, will send all messages as privmsgs (if commented out,
# it will send as Notices) *NOTE:* This option Violates IRC RFC, and
# can cause flooding problems on your network. Its NOT recommended.
UsePrivmsg = false

# OPERONLY =
[OPTIONAL]
# Restrict NeoStats and StatServ to opers use only.
# If not specified, users will have some access to NeoStats
# and StatServ commands. e.g.
#
# OPERONLY=true
#
# Only opers may use NeoStats and StatServ.
OperOnly = false

# SERVERSETTIME= [OPTIONAL]
# Cause NeoStats to sync server times at the given interval
# INTERVAL is an integer representing the number of hours
#
# Examples
#
# SERVERSETTIME=24
#
# Cause NeoStats to sync server times every 24 hours
# If not present, NeoStats will not sync times.
# This option only works on servers that support this and
# defaults to a sync interval of 24 hours. Enabling this
# option will also cause NeoStats to sync servers when it
# first joins the network.
ServerSettime = 24

# DatabaseType = "" [OPTIONAL]
# Specifies the database manager module to use.
# NeoStats will default to GDBM if this is not provided.
# Valid options are:
# gdbm
# bdb (if found during configure)
#
# DatabaseType = "gdbm"
#
#
DatabaseType = "gdbm"

# LOGFILENAMEFORMAT = "
" [OPTIONAL]
# Defines the format for dated log files. This allows you to choose
# what date format is used for log file names when they are rotated at
# midnight. The option uses the parameters passed to strftime so you
# can use any options valid for that function. Common ones are:
# %a Abbreviated weekday name
# %A Full weekday name
# %b Abbreviated month name
# %B Full month name
# %d Day of month as decimal number (01 – 31)
# %m Month as decimal number (01 – 12)
# %y Year without century, as decimal number (00 – 99)
# %Y Year with century, as decimal number
#
# Examples using 30 September 2003 as the date:
# For NeoStats0930.log:
#
# LOGFILENAMEFORMAT="%m%d"
#
# For NeoStats20030930.log:
#
# LOGFILENAMEFORMAT="%Y%m%d"
#
# If not defined, the default is the original NeoStats log format of
# "-%m-%d" i.e. NeoStats-09-30.log
#LogFileNameFormat = "-%m-%d"

# ROOTNICK = "" [REQUIRED]
# Specifies the nick of the NeoStats root bot
# e.g.
#
# ROOTNICK="NeoStats"
#
# When NeoStats links, it create a root bot with nick NeoStats
RootNick = "NeoStats"

# SERVICESHOST = "" [REQUIRED]
# Specifies the default host of NeoStats service bots
# e.g.
#
# SERVICEHOST="stats.net"
#
# Service bots will now we user@stats.net
# If not specified NeoStats will default to the server name
ServicesHost = "stats.zemra.org"

# NOLOAD = true [YOU MUST REMOVE THIS]
# If this is in the neostats.conf your NeoStats WILL NOT START UP. To
# disable this simply comment this line out. e.g.
#
# NOLOAD = true <- NeoStats will not load.
#
# #NOLOAD = true <- NeoStats will load.
#
# NOLOAD = false <- Neostats will load.
# NOLOAD = true
}

##################################
# NeoStats Linking Configuration #
##################################

# This section defines the Server that NeoStats will
# attempt to link to. You must configure this server
# with the correct C/N and U lines for Neostats

Servers {

# IPADDRESS ="" [REQUIRED]
# Specifies the IP address to connect to. e.g.
#
# IPADDRESS="127.0.0.1"
#
# This will force stats to connect to 127.0.0.1
IpAddress = "72.62.52.42"

# PORT =
[REQUIRED]
# Specifies the port to connect to on the IRC Server e.g.
#
# PORT=6667
#
# When connecting, NeoStats will connect to port 6667
Port = 8888

# PASSWORD="
" [REQUIRED]
# Specifies the password used to connect. This must match your C/N
# lines in your IRCD configuration e.g.
#
# PASSWORD="linkpass"
#
# Send "linkpass" as the password to connect
Password = "LinkPass"
}

########################################
# NeoStats Administrator Configuration #
########################################

ServiceRoot {
#MASK="" [REQUIRED]
# Who should get master access to manage NeoStats regardless of
# authentication systems. Only one entry allowed. e.g.
#
# MASK="fish!?Fish@*.neostats.net"
#
# Will give "fish" complete access to NeoStats if fish has
# umode +r and comes from the specified hostname and ident.
Mask = "DeviL!EviL@*Zemra.Org"
}

#################################
# NeoStats Module Configuration #
#################################

Modules {
#####################################
# Module Configurations and Loading #
#####################################

# MODULENAME = {"", "", ""} [OPTIONAL]
# What modules to load at start-up. e.g.
#
# MODULENAME = { "statserv" }
#
# Will load up StatServ only at boot
#
# To specify NeoStats to load multiple modules, place a comma after
# each module and specify the next one e.g.
#
# MODULENAME = { "statserv", "extauth" }
#
# will load up both statserv and extauth modules
#
# We have provided example lines for convenience for
# official modules but you must download and install
# external modules before trying to load them.

MODULENAME = {

# Update notification module, loaded by default
"update",

# StatServ, maintain and report various networks statistics
"statserv",

# HostServ, vhost services for users
"hostserv",

# TextServ, text messaging service
"textserv",

# ConnectServ, monitor connections to the network: user connections, oper
# modes, server connections and nick changes.
"connectserv",

# Operlog, operator command logging service
"operlog",

# IRCdauth, authenticate users based on their user modes.
"ircdauth",

# Extauth, authenticate users based on nick!user@host access lists
"extauth",

# QuoteServ, Quote Message Service
"quoteserv",

# LimitServ, Channel Limit Setting Service
"limitserv",

# SecureServ. You must download and install SecureServ first.
# "secureserv",

# BLSB. You must download and install BLSB first.
# "blsb",

# OPSB. You must download and install OPSB first.
# "opsb",

# LogServ. You must download and install LogServ first.
# "logserv",

# TriviaServ. You must download and install TriviaServ first.
# "triviaserv",

# WarServ. You must download and install WarServ first.
# "warserv",

# GamesServ. You must download and install GameServ first.
# "gamesserv",

# YahzteeServ. You must download and install YahzteeServ first.
# "yahtzeeserv",

# FloodServ. You must download and install FloodServ first.
# "floodserv",

# SeenServ. You must download and install SeenServ first.
# "seenserv",

# ProfileServ. You must download and install ProfileServ first.
# "profileserv",

}
}

#####################################
# NeoNetConfigurations and Loading #
#####################################

# NeoNet is a protocol that links all NeoStats installations back to the main
# NeoStats sites, such as http://secure.irc-chat.net etc.
# This allows you to take advantage of some of the aditional features or modules
# that we support, such as updated definitions for SecureServ accounts, or
# reporting options for OPSB.

# You must visit http://accounts.neostats.net/ to create your NeoNet account
# and select what aditional options you would like. (some might require 3rd
# party modules, such as SecureServ or OPSB).

# If you have been using SecureServ on the 2.5 series, please visit
# http://accounts.neostats.net/migrate/ for information on how to
# use your existing Secure.irc-chat.net account with NeoNet.
NeoNet {

# This is the username, as supplied on the NeoNet pages.
# It should be your IRC Network user account and not your
# personal accounts.
# UserName = "somenet"

# This is your IRC Network User account password.
# PassWord = "password"

# Leave the port at 2960 unless otherwise instructed.
# Port = 2960

# This option handles how NeoNet connections are established. The available
# options are:
# yes - Connect to NeoNet during startup
# no - Never connect to NeoNet (Note, some features might not work if Connect
# is set to No
# demand - Only connect to NeoNet when there is a pending NeoNet Message
# to be sent.
Connect = "yes"
}

###############################################################################
## End of Configuration ##
###############################################################################

Edited by DeviL
Irc.Zemra.Org
www.Zemra.Org
Email: Info@Zemra.Org