View and vote on the article here: CAIRC - IRC Servers
CAIRC - IRC Servers| Category | | | Summary | | | Body | ::-=IRC Servers ~np~[CAIRC 101]~/np~ =-::
~np~Welcome to CAIRC 101
Delivered for the purpose of Staff Training and general knowledge.
All questions should be directed to ben981 (rootdrop@rootdropped.co.uk),
fallen1 (aoa_antime_1@hotmail.com) or Borgdrone (foul_demon@hotmail.com).
~np~The class is divided into four sections:~/np~
~np~Section 1 - MemoServ~/np~
~np~Section 2 - NickServ~/np~
~np~Section 3 - ChanServ~/np~
~np~Section 4 - HostServ~/np~
~np~The overall time of this class is expected to run 45 - 60 minutes. If
you can't stay during the whole class, logs will be provided later. Our
assistant is Helper. If you have any questions during the class, they
can be asked by typing:~/np~
~np~/msg Helper !ask ~/np~
~np~If anybody abuses Helper, you will be kicked and banned.~/np~
~np~A note about syntax before we begin (for those of you who don't look at
command syntax every day). Words in brackets ('[' and ']') are optional.
Words that appear between braces ('{' and '}') and seperated by a pipe
('|') means you must include at least one of the options. Now that all
of that is out of the way, we can begin the class.~/np~
::-=~np~Section 1 :: MemoServ~/np~ =- ::
~np~MemoServ is a utility allowing IRC users to send short messages to other
IRC users (or channels), whether they are online at the time or not.
Both the sender's nickname and the target nickname (or channel) must be
registered in order to send a memo.~/np~
~np~[NOTE] By default, you need level 10 access to send a memo to a channel.~/np~
~np~MemoServ's commands include:~/np~
~np~SEND Send a memo to a nick or channel ~/np~
~np~LIST List your memos ~/np~
~np~READ Read a memo or memos ~/np~
~np~DEL Delete a memo or memos ~/np~
~np~SET Set options related to memos~/np~
~np~We'll discuss the commands listed above in the order they appear.
Here's how the SEND command works:~/np~
~np~Syntax: /msg MemoServ SEND {nick | channel} memo-text~/np~
~np~SEND sends the named nick or channel a memo containing memo-text.
When sending to a nickname, the recipient will receive a notice that
he/she has a new memo. The target nickname/channel must be registered.
So, for example, if I wanted to send a memo to marshal dimplesx, I would
simply type this:~/np~
~np~/msg MemoServ SEND Di]v[pLeS Hey, what's up?~/np~
~np~And voila, she's got a memo waiting for her. As you'll soon see, all of
MemoServ's commands are as simple as the SEND command. Now let me show
you how to use the LIST command to get a listing of all of your memos.~/np~
~np~Syntax: /msg MemoServ LIST [channel] [list | NEW]~/np~
~np~LIST lists any memos you currently have. With NEW, it will list only
new (unread) memos. Unread memos are marked with an asterisk (*) to the
left of the memo number. You can also specify a list of numbers, as in
the example below:~/np~
~np~/msg MemoServ LIST 3-7~/np~
~np~Lists memos numbered 3 through 7.~/np~
~np~OK. Now that you can get a listing of your memos, you'll probably want
to read them. Here's how you read your memos:~/np~
~np~Syntax: /msg MemoServ READ [channel] {num | list | LAST | NEW}~/np~
~np~READ sends you the text of the memo(s) specified. If LAST is given,
read sends you the memo you most recently received. If NEW is given,
read sends you all of your new memos. Otherwise, read sends you memo
number num. You can also give a list of numbers, as in this example:~/np~
~np~/msg MemoServ READ 3-7~/np~
~np~Displays memos 3 through 7.~/np~
~np~When you have finished reading a memo, you will probably want to get rid
of it. After all, you can only have 20 memos at a time. Let me show you
how to use the DEL command to, obviously, delete memos:~/np~
~np~Syntax: /msg MemoServ DEL [channel] {num | ALL}~/np~
~np~DEL deletes the specified memo(s). You can supply multiple memo numbers
or ranges of numbers instead of a single number, as in the second example
below. If ALL is given, del deletes all of your memos.~/np~
~np~/msg MemoServ DEL 1~/np~
~np~Deletes your first memo.~/np~
~np~/msg MemoServ DEL 3-7~/np~
~np~Deletes memos numbered 3 through 7.~/np~
~np~The only thing left for you to learn about MemoServ is how to set when
you are notified of new memos, and how to set the max number of memos you
can receive. Here's how you set these options:~/np~
~np~Syntax: /msg MemoServ SET option parameters~/np~
~np~SET sets various memo options. option can be one of:~/np~
~np~NOTIFY~/np~ ~np~Changes when you will be notified of new memos~/np~
~np~LIMIT~/np~ ~np~Sets the maximum number of memos you can receive~/np~
~np~The NOTIFY option is used like this:~/np~
~np~Syntax: /msg MemoServ SET NOTIFY {ON | LOGON | NEW | OFF}~/np~
~np~NOTIFY changes when you will be notified of new memos. Here's what the
parameters do:~/np~
~np~ON~/np~ ~np~You will be notified of memos when you log on, when you unset~/np~
~np~/AWAY, and when they are sent to you.
~np~LOGON~/np~ ~np~You will only be notified of memos when you log on or when you~/np~
~np~unset /AWAY.~/np~
~np~NEW~/np~ ~np~You will only be notified of memos when they are sent to you.~/np~
~np~OFF~/np~ ~np~You will not receive any notification of memos.~/np~
~np~[NOTE] ON is equivalent to LOGON and NEW combined.~/np~
~np~Note that if your nickname has the "secure" setting on, you will only be
notified of new memos (for LOGON or ON) after you identify. And finally,
here's how you set the max number of memos you can receive:~/np~
~np~Syntax: /msg MemoServ SET LIMIT [channel] limit~/np~
~np~LIMIT sets the maximum number of memos you (or the given channel) are
allowed to have. If you set this to 0, no one will be able to send any
memos to you. However, you cannot set this any higher than 20.~/np~
~np~This concludes section one. If you have any questions, type:~/np~
~np~/msg Helper !ask~/np~
.:back to top
::-=~np~Section 2 :: NickServ~/np~=-::
~np~NickServ allows you to "register" a nickname and prevent others from
using it. If the nick is not used for 30 days, the registration will
expire. The following commands allow for registration and maintenance
of nicknames:~/np~
~np~REGISTER~/np~ ~np~Register a nickname~np~
~np~IDENTIFY~/np~ ~np~Identify yourself with your password~/np~
~np~ACCESS~/np~ ~np~Modify the list of authorized addresses~/np~
~np~LINK~/np~ ~np~Make your nick an alias for another~/np~
~np~UNLINK~/np~ ~np~Removes the link between two nicks~/np~
~np~SET~/np~ ~np~Set options, including kill protection~/np~
~np~UNSET~/np~ ~np~Unsets various options~/np~
~np~DROP~/np~ ~np~Cancel the registration of a nickname~/np~
~np~RECOVER~/np~ ~np~Kill another user who has taken your nick~/np~
~np~RELEASE~/np~ ~np~Regain custody of your nick after RECOVER~/np~
~np~GHOST~/np~ ~np~Used to remove the "ghost" of a nick~/np~
~np~INFO~/np~ ~np~Retrieves various nick information~/np~
~np~LIST~/np~ ~np~Lists all nicks matching the specified filter~/np~
~np~STATUS~/np~ ~np~Displays a nick's status code~/np~
~np~We'll discuss the commands listed above in the order they appear. Here's
how the REGISTER command works:~/np~
~np~Syntax: /msg NickServ REGISTER password email
~np~REGISTER 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! MOKI, Moki, and moki are all different passwords!)~/np~
~np~[NOTE] Be nice to the IRCops. Use your real e-mail adderss. I have seen
tons of people get mad at IRCops for not handing over access to a nick. If
you forget your nick's password, the only thing an IRCop can do for you is
have the password sent to the e-mail that was used during registration. If
you use a fake e-mail, and forget your password, you're screwed. Don't bug
the IRCops. There is no way for them to verify you are the owner of the
nick~/np~
~np~Guidelines on choosing passwords:~/np~
~np~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.~/np~
~np~Now that you have your nick registered, you'll need to identify to
NickServ every time you logon to IRC. That proves you are the owner of
the nick. Here's how:~/np~
~np~Syntax: /msg NickServ IDENTIFY password~/np~
~np~IDENTIFY 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.~/np~
~np~There are other ways of identifying yourself to NickServ. You have to
use the ACCESS command. Here's how you use ACCESS:~/np~
~np~Syntax: /msg NickServ ACCESS {ADD | DEL} mask~/np~
~np~ACCESS 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.~/np~
~np~Examples:~/np~
~np~/msg NickServ ACCESS ADD achurch@*.dragonfire.net~/np~
~np~Allows access to user achurch from any machine in the dragonfire.net
domain.~/np~
~np~/msg NickServ ACCESS DEL achurch@*.dragonfire.net~/np~
~np~Reverses the previous command.~/np~
~np~/msg NickServ ACCESS LIST~/np~
~np~Displays the current access list.~/np~
~np~Most people don't have any real reason to use the ACCESS command. Now
I'm going to show you a really useful command. Well, it's only useful if
you have more than one nick registered. But that's a lot of people.
This command is the LINK command. Let's say you have a nick that is on
the access list for several channels. Now you want to use another nick.
So you go ahead and register another nick. Now, instead of bugging the
channel ops to put your new nick on the access list, you can simply link
your new nick to your old nick. Any privileges your other nick has, your
new nick will also have. Here's how you link to another nick:~/np~
~np~Syntax: /msg NickServ LINK nick password~/np~
~np~LINK links your nickname to another, effectively making the nick you are
currently using an alias for the given nick. When you give this command,
the access list for the nick you are using is deleted and replaced by
that of the nick you are linking to; all memos for your current nick are
added to the list of memos for the target nick (this may cause the nick
to exceed its limit of memos, in which case you will need to delete some
before you can receive more for either nick).~/np~
~np~Once the link has been established, your nick will be transparently
converted into the target nick everywhere in Services, except for the
NickServ UNLINK and DROP commands. For example, you can use either nick
to read the same set of memos (and memos sent to either nick will go into
the same list). If either nick is on a channel's access list, then both
nicks will get the same access privileges. However, the nicks will expire
independently; if you only use one of a set of linked nicks, all the rest
will expire.~/np~
~np~In order to use this command, you must identify for your current nick
(using the IDENTIFY command), and you must supply the password for the
nick you wish to link to. You can also UNLINK a nick. The syntax is the
same as that for the LINK command, except you replace the word LINK with
UNLINK.~/np~
~np~I'm now going to tell you about several other commands that you may find
useful. These are the PASSWORD, LANGUAGE, URL, EMAIL, KILL, SECURE,
PRIVATE, and HIDE options. In order to use these commands, you must first
identify with your password.~/np~
~np~The password option, quite simply, allows you to change your password. It
is used like so:~/np~
~np~Syntax: /msg NickServ SET PASSWORD new-password~/np~
~np~The LANGUAGE command changes the language Services uses when sending
messages to you (for example, when responding to a command you send). You
use it like this:~/np~
~np~Syntax: /msg NickServ SET LANGUAGE number~/np~
~np~number should be chosen from the following list of supported languages:~/np~
~np~1) English~/np~
~np~2) Italian~/np~
~np~3) Japanese / EUC encoding~/np~
~np~4) Japanese / SJIS encoding~/np~
~np~5) Portugues (Portuguese)~/np~
~np~6) Español (Spanish)~/np~
~np~7) Turkce (Turkish)~/np~
~np~The URL command associates the given URL with your nickname. This URL
will be displayed whenever someone requests information on your nick with
the INFO command. The syntax is:~/np~
~np~Syntax: /msg NickServ SET URL url~/np~
~np~The EMAIL command associates the given E-mail address with your nickname.
This address will be displayed whenever someone requests information on
the channel with the INFO command. It is set like this:~/np~
~np~Syntax: /msg NickServ SET EMAIL address~/np~
~np~Now here is an option that everybody should have set. It's the KILL
option. KILL turns the automatic kill protection option for your nick on
or off. With kill protection on, if another user tries to take your nick,
they will be given one minute to change to another nick, after which they
will be forcibly removed from IRC by NickServ. If you select QUICK, the
user will be given only 20 seconds to change nicks instead of the usual 60.
If you select IMMED, the user will be killed 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.~/np~
~np~You set KILL like so:~/np~
~np~Syntax: /msg NickServ SET KILL {ON | QUICK | IMMED | OFF}~/np~
~np~Here is a command that works hand-in-hand with KILL. This is SECURE.
SECURE 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. To turn it on or off,
use this syntax:~/np~
~np~Syntax: /msg NickServ SET SECURE {ON | OFF}~/np~
~np~Onto the PRIVATE command. Private 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.) Here's how:~/np~
~np~Syntax: /msg NickServ SET PRIVATE {ON | OFF}~/np~
~np~Now I'm going to show you how to use the HIDE command. HIDE 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), and last quit message (QUIT).
The second parameter specifies whether the information should be displayed
(OFF) or hidden (ON).~/np~
~np~Syntax: /msg NickServ SET HIDE {EMAIL | USERMASK | QUIT} {ON | OFF}~/np~
~np~There is also an UNSET command. You have the option of unsetting your
e-mail and your nick's URL. However, you can't actually UNSET your e-mail
address. There really isn't any reason to anyways, because if you're
worried about somebody obtaining your address, you can just hide it :)~/np~
~np~So, to UNSET your URL, just type this:~/np~
~np~/msg NickServ UNSET URL~/np~
~np~Now what if you wanted to drop (unregister) your nick? Well, that's easy,
too. You use the DROP command. DROP drops your nickname from the NickServ
database. A nick that has been dropped is free for anyone to re-register.
It is used like this:~/np~
~np~/mgs NickServ DROP~/np~
~np~The next three commands can be very useful. These are the RECOVER,
RELEASE, and GHOST commands. RECOVER 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 will remain
online for one minute to ensure that the other user does not immediately
reconnect; after that minute, you can reclaim your nick. Alternatively,
use the RELEASE command 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, or you must supply the correct password for
the nickname. To use these commands, you would type:~/np~
~np~Syntax: /msg NickServ {RECOVER | RELEASE} nickname password~/np~
~np~This next command, GHOST, is probably the most useful out of the bunch.
GHOST 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. This could be because your ISP
disconnects you every two hours, you just got disconnected for some weird
reason, you had a power surge, or whatever. 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, or you must supply the correct password for the nick.
Here's how you GHOST a nick:~/np~
~np~Syntax: /msg NickServ GHOST nickname [password]~/np~
~np~There are only three NickServ commands left. These are INFO, LIST, and
STATUS. INFO 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. INFO is used like this:~/np~
~np~Syntax: /msg NickServ INFO nickname [ALL]~/np~
~np~LIST lists all registered nicknames which match the given pattern, in
nick!user@host format. Nicks with the PRIVATE option set will not be
displayed. The syntax is:~/np~
~np~/msg NickServ LIST pattern~/np~
~np~Examples:~/np~
~np~/msg NickServ LIST *!joeuser@foo.com~/np~
~np~Lists all nicks owned by joeuser@foo.com.~/np~
~np~/msg NickServ LIST *Bot*!*@*~/np~
~np~Lists all registered nicks with Bot in their names (case insensitive).~/np~
~np~/msg NickServ LIST *!*@*.bar.org~/np~
~np~Lists all nicks owned by users in the bar.org domain.~/np~
~np~Finally, the STATUS command. It is used like this:~/np~
~np~Syntax: /msg NickServ STATUS nickname...~/np~
~np~STATUS returns whether the user using the given nickname is recognized as
the owner of the nickname. The response has this format:~/np~
~np~nickname status-code~/np~
~np~where nickname is the nickname sent with the command, and status-code is
one of the following:~/np~
~np~0 - no such user online or nickname not registered~/np~
~np~1 - user not recognized as nickname's owner~/np~
~np~2 - user recognized as owner via access list only~/np~
~np~3 - user recognized as owner via password identification~/np~
~np~Up to sixteen nicknames may be sent with each command; the rest will be
ignored. No error message is generated if no nickname is given.~/np~
~np~This concludes section two. If you have any questions, type:~/np~
~np~/msg Helper !ask ~/np~
.:back to top
::-=~np~Section 3 :: ChanServ~/np~=-::
ChanServ allows you to register and control various aspects of channels.
ChanServ can often prevent malicious users from "taking over" channels by
limiting who is allowed channel operator privileges. Available commands are
listed below:
REGISTER Register a channel
IDENTIFY Identify yourself with your password
DROP Cancel the registration of a channel
INFO Show channel options and information
SET Set channel options and information
ACCESS Maintain the overall channel access list
SOP Maintain the SuperOp list
AOP Maintain the AutoOp list
VOP Maintain the AutoVoice list
AKICK Maintain the AutoKick list
Other commands: UNSET, LIST, INVITE, UNBAN, CLEAR,
LEVELS, OP, DEOP, VOICE, DEVOICE,
HALFOP, DEHALFOP, PROTECT, DEPROTECT,
HOP
~np~[NOTE] Any channel which is not used for 14 days (i.e. which no user on the
channel's access list enters for that period of time) will be automatically
dropped.~/np~
Like the discussions on MemoServ and NickServ, I will be going over the
commands listed above in the order that they appear. So, we'll begin this
discussion with how to register a channel.
Syntax: /msg ChanServ REGISTER channel password description
Example: /msg ChanServ REGISTER #help-training p4rity8 Welcome
to #help-training!
REGISTER registers a channel in the ChanServ database. In order to use this
command, you must first be a channel operator on the channel you're trying to
register. The password is used with the IDENTIFY command to allow you to make
changes to the channel settings at a later time. The last parameter, which
must be included, is a general description of the channel's purpose.
When you register a channel, you are recorded as the "founder" of the channel.
The channel founder is allowed to change all of the channel settings for the
channel; ChanServ will also automatically give the founder chanop privileges
when he/she enters the channel.
~np~[NOTE] In order to register a channel, you must have first registered your
nick.~/np~
To identify yourself as the channel's founder, you use the IDENTIFY command,
like this:
Syntax: /msg ChanServ IDENTIFY channel password
Example: /msg ChanServ IDENTIFY #help-training p4rity8
IDENTIFY authenticates you to ChanServ as the founder of the given channel.
Many commands require you to use this command before using them. The password
should be the same one you sent with the REGISTER command.
You can also drop (unregister) a channel by using the DROP command.
Syntax: /msg ChanServ DROP channel
Example: /msg ChanServ DROP #help-training
If you need (or want) to get information on a channel, you can use the INFO
command. It is used like this:
~np~Syntax: /msg ChanServ INFO channel [ALL]~/np~
Example: /msg ChanServ INFO #help-training ALL
INFO lists information about the named registered channel, including its
founder, time of registration, last time used, description, and mode lock
(if any). If you are identified as the founder of the channel you're getting
information for, and ALL is specified, the entry message and successor will
also be displayed.
Now we get to the fun command; SET. SET is the command that offers us all of
the cool options. You set an option like this:
Syntax: /msg ChanServ SET channel option parameters
Here are the available options:
FOUNDER Set the founder of a channel
SUCCESSOR Set the successor for a channel
PASSWORD Set the founder password
DESC Set the channel description
URL Associate a URL with the channel
EMAIL Associate an E-mail address with the channel
ENTRYMSG Set a message to be sent to users when they enter the channel
TOPIC Change the topic on the channel
KEEPTOPIC Retain topic when channel is not in use
TOPICLOCK Topic can only be changed with SET TOPIC
MLOCK Lock channel modes on or off
PRIVATE Hide channel from LIST command
RESTRICTED Restrict access to the channel
SECURE Activate ChanServ security features
SECUREOPS Stricter control of chanop status
LEAVEOPS Do not de-op users on channel entry
OPNOTICE Send a notice when OP/DEOP commands are used
ENFORCE Enforce auto-op, auto-voice status
To change the channel's founder, you would enter:
Syntax: /msg ChanServ SET channel FOUNDER nick
Example: /msg ChanServ SET #help-training FOUNDER Fallen1
You can also set the channel's success. The syntax is the same, except you
use the word SUCCESSOR instead of FOUNDER. If the founder's nickname expires
or is dropped while the channel is still registered, the successor will become
the new founder of the channel. However, if the successor already has too
many channels registered (20), the channel will be dropped instead, just as
if no successor had been set. The new nickname must be a registered one.
If you want to give the successor the password for the channel, so that they
can have the same power as you, no problem. But what if you use that password
for everything? You don't want the successor having the password to your
e-mail, online bank account, or whatever else you use that password for. Why
not change the channels password? Here's how:
Syntax: /msg ChanServ SET channel PASSWORD password
Example: /msg ChanServ SET #help-training PASSWORD ilovelinux
~np~[NOTE] These commands don't flow from one to the other. So it's going to look
like I'm jumping from command to command. Because I am :)~/np~
To set the channel's description, you use the DESC command.
Syntax: /msg ChanServ SET channel DESC description
You can also set the channel's URL and EMAIL.
Syntax: /msg ChanServ SET channel {URL | EMAIL} url_or_e-mail
Now for the ENTRYMSG command. This commands allows you to send a message to
everybody that joins your chanel. It sends the message via a /NOTICE.
Syntax: /msg ChanServ SET channel ENTRYMSG message
Example: /msg ChanServ SET #help-training ENTRYMSG phj33r d4 z3br4!
Now, whenever people join your channel, they will see this:
*** Now talking in #help-training
*** ChanServ sets mode: +oaq Moki Moki Moki
-ChanServ- phj33r d4 z3br4!
Of course, replace the message, user, modes, and channel with whatever you
want.
Ok, now onto JOIN
Syntax: /msg ChanServ SET channel JOIN {ON | OFF}
Enables or disables the Join options for a channel. When set, ChanServ will
join the channel and listen for triggers typed in the channel by users.
~np~The following triggers are understood by ChanServ:~np~
~np~!op []~/np~ ~np~!deop []~/np~
~np~!halfop []~/np~ ~np~!dehalfop []~/np~
~np~!voice []~/np~ ~np~!devoice []~/np~
~np~!protect []~/np~ ~np~!deprotect []~/np~
The triggers work like aliases for their equivalent ChanServ commands. A
user cannot use a trigger to which they would not normally be entitled access.
Now we look at TOPIC;
Syntax: /msg ChanServ SET channel TOPIC topic
Causes ChanServ to set the channel topic to the one specified. This command
is most useful when someone has set TOPICLOCK.
This is how we set KEEPTOPIC.
Syntax: /msg ChanServ SET channel KEEPTOPIC {ON | OFF}
Enables or disables the topic retention option for a channel. When topic
retention is set, the topic for the channel will be remembered by ChanServ
even after the last user leaves the channel, and will be restored the next
time the channel is created.
Now, the most annoying option of them all! TOPICLOCK
Syntax: /msg ChanServ SET channel TOPICLOCK {ON | OFF}
Enables or disables the topic lock option for a channel. When topic lock
is set, ChanServ will not allow the channel topic to be changed except via
the SET TOPIC command.
MLOCK, can be very usefull, especially if you specifically want certain
modes for your chan.
Syntax: /msg ChanServ SET channel MLOCK modes
Sets the mode-lock parameter for the channel. ChanServ allows you to choose
certain channel modes to be always on (or off). The modes that can be locked
are i, k, l, m, n, p, s, and t; each of these modes can be locked on, locked
off, or not locked. The modes parameter is constructed exactly the same way
as a /MODE command; that is, modes followed by a + are locked on, and modes
followed by a - are locked off.
Warning: If you set a mode-locked key, as in the second example below, you
should also set the RESTRICTED option for the channel (see HELP SET
RESTRICTED), or anyone entering the channel when it is empty will be able to
see the key!
Examples:
SET #channel MLOCK +nt-iklps
Forces modes n and t on, and modes i, k, l, p, and s off. Mode m is left free
to be either on or off.
SET #channel MLOCK +knst-ilmp my-key
Forces modes k, n, s, and t on, and modes i, l, m, and p off. Also forces
the channel key to be "my-key".
SET #channel MLOCK +
Removes the mode lock; all channel modes are free to be either on or off.
Now we go on to PRIVATE, very useful for keeping your chan a secret!
Syntax: /msg ChanServ SET channel PRIVATE {ON | OFF}
Enables or disables the private option for a channel. When private is set, a
/msg ChanServ LIST will not include the channel in any lists.
On to RESTRICTED!
Syntax: /msg ChanServ SET channel RESTRICTED {ON | OFF}
Enables or disables the restricted access option for a channel. When restricted
access is set, users who would normally be disallowed from having channel
operator privileges (users with negative access levels and, if secure ops is
set, users not on the access list) will instead be kicked and banned from the
channel.
Dya wanna SECURE your chan?
Syntax: /msg ChanServ SET channel SECURE {ON | OFF}
Enables or disables ChanServ's security features for a channel. When SECURE
is set, only users who have registered their nicknames with NickServ and
IDENTIFY'd with their password will be given privileges on the channel as
controlled by the access list.
SECUREOPS, good for stopping people trying the "halfop" trick on CS in your
chan
Syntax: /msg ChanServ SET channel SECUREOPS {ON | OFF}
Enables or disables the secure ops option for a channel. When secure ops is
set, users who are not on the userlist will not be allowed chanop status.
LEAVEOPS!! Everyone's dream!
Syntax: /msg ChanServ SET channel LEAVEOPS {ON | OFF}
Enables or disables the leave ops option for a channel. When leave ops is set,
ChanServ will leave server ops (+o for the first person in the channel) in
place even if the user would not normally get auto-opped. The SECUREOPS option
and AUTODEOP access level will still be enforced. Notice: This can allow users
to "steal" ops during a netsplit. (ack, a netsplit, /me shudders...)
OPNOTICE, is it just me? Or is this really boring...
Syntax: /msg ChanServ SET channel OPNOTICE {ON | OFF}
Enables or disables the op-notice option for a channel. When op-notice is set,
ChanServ will send a notice to the channel whenever the OP or DEOP commands
are used for a user in the channel.
Use the ENFORCE Luke!
Syntax: /msg ChanServ SET channel ENFORCE {ON | OFF}
Enables or disables the enforce option for a channel. When enforce is set,
ChanServ will enforce the auto-op and auto-voice levels for all users. For
example, if a user with auto-op privileges is deopped, ChanServ will
automatically op the user again, and ChanServ will also not allow the DEOP
command to be used on that user.
ACCESS, the thing we all love most...
Note that any channel which is not used for 14 days (i.e. which no user on
the channel's access list enters for that period of time) will be
automatically dropped.
Syntax: /msg ChanServ ACCESS channel ADD nick level
/msg ChanServ ACCESS channel DEL {nick | entry-num | list}
/msg ChanServ ACCESS channel LIST [mask | list]
/msg ChanServ ACCESS channel COUNT
Maintains the access list for a channel. The access list specifies which
users are allowed chanop status or access to ChanServ commands on the
channel. Different user levels allow for access to different subsets
of privileges; /msg ChanServ HELP ACCESS LEVELS for more specific information.
Any nick not on the access list has a user level of 0. Note that the access
list may also be manipulated with the SOP, AOP, and VOP commands, which
correspond to levels of 10, 5, and 3 respectively.
The ACCESS ADD command adds the given nickname to the access list with the
given user level; if the nick is already present on the list, its access
level is changed to the level specified in the command. The level specified
must be less than that of the user giving the command, and if the nick is
already on the access list, the current access level of that nick must be
less than the access level of the user giving the command. The ACCESS DEL
command removes the given nick from the access list. If a list of entry
numbers is given, those entries are deleted. (See the example for LIST
below.) The ACCESS LIST command displays the access list. If a wildcard
mask is given, only those entries matching the mask are displayed. If a list
of entry numbers is given, only those entries are shown; for example:
/msg ChanServ ACCESS #channel LIST 2-5,7-9
Lists access entries numbered 2 through 5 and 7 through 9.
The ACCESS COUNT command returns the number of entries there are on the access
list.
Is it a bird? Is it a plane? No, it's SUPEROP!
The ACCESS COUNT command returns the number of entries there are on the access
list.
Syntax: /msg ChanServ SOP channel ADD nick
/msg ChanServ SOP channel DEL nick
/msg ChanServ SOP channel LIST [mask | list]
/msg ChanServ SOP channel COUNT
Maintains the SuperOp (SOP) list for a channel. Users with SOP status are
automatically opped (set mode +o) and protected (mode +a) when they join the
channel.
An SOP can modify the AOP and VOP lists. Only a channel's founder can modify
the SOP list. The SOP LIST command displays the SOP list. If a wildcard
mask is given, only those entries matching the mask are displayed. If a
list of entry numbers is given, only those entries are shown; for example:
/msg ChanServ SOP #channel LIST 2-5,7-9
Lists SOP list entries numbered 2 through 5 and 7 through 9.
The SOP COUNT command returns the number of entries there are on the SOP list.
AOP's I did it again... wha' that isn't the words? Oh well...
Syntax: /msg ChanServ AOP channel ADD nick
/msg ChanServ AOP channel DEL nick
/msg ChanServ AOP channel LIST [mask | list]
/msg ChanServ AOP channel COUNT
Maintains the AutoOp (AOP) list for a channel.
Users with AOP status are automatically opped (set mode +o) when they join
the channel. An AOP can modify the VOP list.
The AOP LIST command displays the AOP list. If a wildcard mask is given, only
those entries matching the mask are displayed. If a list of entry numbers is
given, only those entries are shown; for example:
/msg ChanServ AOP #channel LIST 2-5,7-9
Lists AOP list entries numbered 2 through 5 and 7 through 9.
The AOP COUNT command returns the number of entries there are on the AOP list.
*all our pain
how did we ever get by without you?
You're so vain
I bet you think this song is about you*
/me bops to NIN
Errrmm... where was I?
Ah!
VOP
Syntax: /msg ChanServ VOP channel ADD nick
/msg ChanServ VOP channel DEL nick
/msg ChanServ VOP channel LIST [mask | list]
/msg ChanServ VOP channel COUNT
Maintains the VoiceOp (VOP) list for a channel.
Users with VOP status are automatically voiced (set mode +v) when they join
the channel. The VOP LIST command displays the VOP list. If a wildcard mask
is given, only those entries matching the mask are displayed. If a list of
entry numbers is given, only those entries are shown; for example:
/msg ChanServ VOP #channel LIST 2-5,7-9
Lists VOP list entries numbered 2 through 5 and 7 through 9.
The VOP COUNT command returns the number of entries there are on the VOP list.
Hehehe, AKICK!
Syntax: /msg ChanServ AKICK channel ADD mask [reason]
/msg ChanServ AKICK channel DEL mask
/msg ChanServ AKICK channel LIST [mask | list]
/msg ChanServ AKICK channel VIEW [mask | list]
/msg ChanServ AKICK channel ENFORCE
/msg ChanServ AKICK channel COUNT
Maintains the AutoKick list for a channel. If a user on the AutoKick list
attempts to join the channel, ChanServ will ban that user from the channel,
then kick the user.
The AKICK ADD command adds the given nick or usermask to the AutoKick list.
If a reason is given with the command, that reason will be used when the user
is kicked; if not, the default reason is "You have been banned from the channel".
The AKICK DEL command removes the given nick or mask from the AutoKick list.
It does not, however, remove any bans placed by an AutoKick; those must be
removed manually.
The AKICK LIST command displays the AutoKick list, or optionally only those
AutoKick entries which match the given mask. AKICK VIEW simply shows more
details.
The AKICK ENFORCE command causes ChanServ to enforce the current AKICK list
by removing those users who match an AKICK mask. The AKICK COUNT command
returns how many entries there are on the AutoKick list.
UNSET, nice and easy.
Syntax: /msg ChanServ UNSET channel {SUCCESSOR | URL | EMAIL | ENTRYMSG}
Clears the given setting for a channel.
LIST, another easy one.
Syntax: /msg ChanServ LIST pattern
Lists all registered channels matching the given pattern. (Channels with the
PRIVATE option set are not listed.)
INVITE
Syntax: /msg ChanServ INVITE channel
Tells ChanServ to invite you into the given channel. By default, only works
if your access level on that channel is at least 5 (op).
CLEAR, /me chuckles, this is a guddun!
Syntax: /msg ChanServ CLEAR channel what
Tells ChanServ to clear certain settings on a channel. What can be any of
the following:
MODES Clears all modes on the channel except those set in the
channel's mode lock.
BANS Clears all bans on the channel.
EXCEPTIONS Clears all exceptions on the channel.
OPS Removes channel-operator status (mode +o) from all users.
HALFOPS Removes halfop status (mode +h) from all users.
VOICES Removes "voice" status (mode +v) from all users.
USERS Removes (kicks) all users from the channel.
By default, your access level on the channel must be at least 10 to use this
command. (Have fun!!!)
_____[WARNING: FOR EXPERIENCED USERS ONLY]_____
LEVELS
Syntax: /msg ChanServ LEVELS channel SET type level
/msg ChanServ LEVELS channel {DIS | DISABLE} type
/msg ChanServ LEVELS channel LIST
/msg ChanServ LEVELS channel RESET
The LEVELS command allows fine control over the meaning of the numeric access
levels used by the ACCESS command. With this command, you can define the
access level required for most of ChanServ's functions. (The SET FOUNDER and
SET PASSWORD commands, as well as this command, are always restricted to the
channel founder.)
LEVELS SET allows the access level for a function or group of functions to be
changed. LEVELS DISABLE (or DIS for short) disables an automatic feature or
disallows access to a function by anyone other than the channel founder.
LEVELS LIST shows the current levels for each function or group of functions.
LEVELS RESET resets the levels to the default levels of a newly-created channel
(see HELP ACCESS LEVELS).
For a list of the features and functions whose levels can be set, see
HELP LEVELS DESC.
Now get ready this is going to be really hard... OP!
Syntax: /msg ChanServ OP #channel nick
Ops a selected nick on a channel. By default, limited to those with level 5
access and above on the channel.
DEOP
Syntax: /msg ChanServ DEOP #channel nick
Deops a selected nick on a channel. By default, limited to those with level
5 access and above on the channel.
VOICE
Syntax: /msg ChanServ VOICE #channel nick
Voices a selected nick on a channel. By default, limited to those with level
3 access and above on the channel.
DEVOICE
Syntax: /msg ChanServ DEVOICE #channel nick
Devoices a selected nick on a channel. By default, limited to those with level
3 access and above on the channel.
HALFOP
Syntax: /msg ChanServ HALFOP #channel nick
Gives halfop access to a selected nick on a channel. By default, limited to
those with level 4 access and above on the channel.
DEHALFOP
Syntax: /msg ChanServ DEHALFOP #channel nick
Removes halfop access from a selected nick on a channel. By default, limited
to those with level 4 access and above on the channel.
PROTECT
Syntax: /msg ChanServ PROTECT #channel nick
Gives channel protection (mode +a) to a selected nick on a channel. By default,
limited to those with level 15 access and above on the channel.
DEPROTECT
Syntax: /msg ChanServ DEPROTECT #channel nick
Removes channel protection (mode -a) to a selected nick on a channel. By
default, limited to those with level 10 access and above on the channel.
HOP
Syntax: /msg ChanServ HOP channel ADD nick
/msg ChanServ HOP channel DEL nick
/msg ChanServ HOP channel LIST [mask | list]
/msg ChanServ HOP channel COUNT
Maintains the HalfOp (HOP) list for a channel. Users with HOP status are
automatically halfopped (set mode +h) when they join the channel.
An HOP can modify the VOP list; SOPs and AOPs can modify the HOP list.
The HOP LIST command displays the HOP list. If a wildcard mask is given, only
those entries matching the mask are displayed. If a list of entry numbers is
given, only those entries are shown; for example:
/msg ChanServ HOP #channel LIST 2-5,7-9
Lists HOP list entries numbered 2 through 5 and 7 through 9.
The HOP COUNT command returns the number of entries there are on the HOP list.
This concludes section three. If you have any questions, type:
/msg Helper !ask
.:back to top
::-=~np~Section 4 :: HostServ~/np~=-::
HostServ allows you to activate and deactivate a virtual host assigned by
an IRC Operator to your nickname. This lets you change your apparent
hostname from something boring like AF7411B3.ipt.aol.com to something more
interesting such as perl.coders.org.
There are only two things you can do with HostServ, so this section is going
to be very small. With HostServ, you can only turn your vhost on, or view
the vhost of another user. Here's how you use ON:
/msg HostServ ON
ON activates your vhost. After issuing the command you will appear to be
connecting from your assigned vhost to other IRC users. If you want to
deactivate your vhost at any time, type:
/mode yournick -x
[NOTE] Whenever you identify to your nick your vhost will be activated
automatically. You only need to use this command to activate your vhost
right after it has been assigned to you, or if you deactivate your vhost.
VIEW is used to view the vhost of another user. It's used like so:
/msg HostServ VIEW nick
If no nickname parameter is supplied, HostServ will show you the vhost that
has been assigned to you. Otherwise, the vhost assigned to the supplied
nickname will be shown.
This concludes section four.
.:back to top
-------
Written by Major Borgdrone & Lt Ker Fallen1
Members of [http://cyberarmy.net|CyberArmy]
-----
{BACKLINKS(info=>hits|user,exclude=>SandBox,include_self=>0,noheader=>0)}{BACKLINKS} |
|
This article was imported from the CyberArmy University site. (original author: PixieLuv)
There are no replies to this post yet.
|