|
| | The following commands supplement the
commands outlined under the Services Help. To list these commands
online, simply type /____Serv HELP (The high-level commands are listed at
the end). OperServ is ONLY available to Opers. Remember that ALL
commands to services are logged.
OperServ - Precede these
commands with /OperServ [command] - For detailed syntax help, type
/OperServ help [command]
IRCops
GLOBAL
- Syntax:
- GLOBAL message
Allows IRCops to send messages to all users on the
network. The message will be sent from the nick Global.
STATS
- Syntax:
- STATS [RESET | AKILL]
Without any option, shows the current number of users
and IRCops online (excluding Services), the highest number of users
online since Services was started, and the length of time Services has
been running.
With the RESET option, resets the maximum user
count to the number of users currently online.
With the AKILL option, displays the current size
of the AKILL list and the current default expiry time.
UPTIME may be used as a
synonym for STATS.
SERVERMAP
- Syntax:
- SERVERMAP
Displays a map of servers connected to the network, from
the viewpoint of Services. "Fake" servers--Services itself and any
servers jupitered with the JUPE command--have "(*)"
displayed after the sever name.
OPER
- Syntax:
- OPER LIST
Any IRC operator may use the OPER LIST form of
the command. All other use limited to Services admins.
ADMIN
- Syntax:
- ADMIN LIST
Any IRC operator may use the ADMIN LIST form of
the command. All other use limited to Services super-user.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
Commands available to Services Operators (SOPs) only:
MODE
- Syntax:
- MODE channel modes
Allows Services operators to set channel modes for any
channel. Parameters are the same as for the standard /MODE
command.
CLEARMODES
- Syntax:
- CLEARMODES channel [ALL]
Clears all binary modes (n,s,t,k,l, and so on) and bans
from a channel. If ALL is given, also clears all user modes (like
+o and +v) from the channel.
CLEARCHAN
- Syntax:
- CLEARCHAN channel
Removes all users from a channel (masskick).
KICK
- Syntax:
- KICK channel user reason
Allows IRCops to kick a user from any channel.
Parameters are the same as for the standard /KICK command. The
kick message will have the nickname of the IRCop sending the KICK
command prepended; for example:
*** SpamMan has been kicked off channel #my_channel
by OperServ (Alcan (Flood))
AKILL
- Syntax:
- AKILL ADD [+expiry] mask reason
AKILL DEL mask
AKILL LIST [mask] [NOEXPIRE]
AKILL VIEW [mask] [NOEXPIRE]
AKILL COUNT
Allows Services operators to manipulate the autokill
(AKILL) list. If a user matching an AKILL mask attempts to connect,
Services will issue a KILL for that user and, on supported server types,
will instruct all servers to add a ban (K-line) for the mask which the
user matched.
AKILL ADD adds the given
user@host mask to the AKILL list for the given reason (which must
be given). AKILL DEL removes the given mask from the AKILL list if
it is present. AKILL LIST shows all current AKILLs; if the
optional mask is given, the list is limited to those AKILLs matching the
mask.
AKILL VIEW is a more verbose version of AKILL LIST, and will
show who added an AKILL, the date it was added, and when it expires, as
well as the user@host mask and reason. If the NOEXPIRE option is
given, then only AKILLs that will not expire, and match the given
user@host mask, will be displayed. AKILL COUNT simply returns the
number of AKILLs in the AKILL list.
Optionally, an expiry time can be given with the
AKILL ADD command. The expiry time precedes the user@host mask, and is
specified as an integer followed by one of "d" (days), "h"
(hours), or "m" (minutes). Combinations (such as 1h30m)
are also permitted. If a unit specifier is not included, the default is
days (so +30 by itself means 30 days). To add an AKILL which
does not expire, use +0. If the usermask to be added starts
with a
+, an expiry time must be given, even if it is the same as the
default. The current AKILL default expiry time can be found with the
STATS AKILL command.
The reason should describe why the entry
is being added; depending on how Services is configured, it may also be
displayed to users in KILL messages.
Services operators may only set an expiry time up to
3 days. Services administrators can always set any expiry time.
EXCLUDE
- Syntax:
- EXCLUDE ADD [+expiry] mask reason
EXCLUDE DEL mask
EXCLUDE LIST [mask] [NOEXPIRE]
EXCLUDE VIEW [mask] [NOEXPIRE]
EXCLUDE COUNT
Allows Services operators to manipulate the autokill
exclusion list. When a user matching an autokill exclusion mask connects
to the network, Services will not issue a KILL for that user even if the
user would otherwise match an autokill mask. This is useful if you have
wide autokill masks, and still want specific hosts or users that match
those masks to be able to connect.
The ADD, DEL, LIST, VIEW, and COUNT subcommands function
the same way as the subcommands for the AKILL command; see the
AKILL help for more information.
KILLCLONES
- Syntax:
- KILLCLONES nick
Kills all users who have the same hostname as
nick. A temporary AKILL, in the form *@host, is added to
prevent the offending clients from immediately reconnecting. A WALLOPS
is also sent indicating who used the command, which host was affected,
and how many users were killed. It's useful for removing numerous clones
from the network.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
Commands available to Services Admins only:
STATS
- Syntax:
- STATS [ALL]
The ALL option is available only to Services
admins, and displays information on Services' memory usage. Using this
option can freeze Services for a short period of time on large networks,
so don't overuse it!
OPER
- Syntax:
- OPER ADD nick
OPER DEL nick
Allows Services admins to add or remove nicknames to or
from the Services operator list. A user whose nickname is on the
Services operator list and who has identified to NickServ will be able
to access Services operator commands.
EXCEPTION (requires the
operserv/sessions
module)
- Syntax:
- EXCEPTION ADD [+expiry] mask limit
reason
EXCEPTION DEL {mask | list}
EXCEPTION MOVE num newnum
EXCEPTION LIST [mask | list]
EXCEPTION VIEW [mask | list]
Allows Services admins to manipulate the list of hosts
that have specific session limits, allowing certain machines, such as
shell servers, to carry more than the default number of clients at a
time. Once a host reaches its session limit, all clients attempting to
connect from that host will be killed. Before the user is killed, they
are notified, via a /NOTICE from OperServ, of a source of help
regarding session limiting.
EXCEPTION ADD adds the
given host mask to the exception list. Note that nick!user@host
and
user@host masks are invalid! Only real host masks, such as
box.host.dom and *.host.dom, are allowed because sessions
limiting does not take nick or user names into account. limit
must be a number greater than or equal to zero; this determines how many
sessions this host may carry at a time (a value of zero means the host
has an unlimited session limit).
Optionally, an expiry time can be given with the
EXCEPTION ADD command. The expiry time precedes the host mask, and is
specified as an integer followed by one of "d" (days), "h"
(hours), or "m" (minutes). Combinations (such as 1h30m)
are also permitted. If a unit specifier is not included, the default is
days (so +30 by itself means 30 days). To add an entry which
does not expire, use +0. If the mask to be added starts with a
+, an expiry time must be given, even if it is the same as the
default.
EXCEPTION DEL removes the
given mask from the exception list.
EXCEPTION MOVE moves
exception num to newnum. If newnum
is already used by another exception, its number will be shifted upward to
make room.
EXCEPTION LIST and
EXCEPTION VIEW show all current exceptions; if the optional mask is
given, the list is limited to those exceptions matching the mask. The
difference between the two commands is that EXCEPTION VIEW is
more verbose, displaying the name of the person who added the exception,
its session limit, reason, host mask and the expiry date and time, as
well as the last time the exception was "used", i.e. the last time a
user connected who matched the exception's mask.
Note that a connecting client will "use" the first
exception their host matches. Large exception lists and widely matching
exception masks are likely to degrade Services' performance.
SESSION
- Syntax:
- SESSION LIST threshold
SESSION VIEW host
Allows Services admins to view the session list.
SESSION LIST lists hosts
with at least threshold sessions. The threshold must be
a number greater than 1, to prevent accidental listing of the large
number of single session hosts.
SESSION VIEW displays
detailed information about a specific host, including the current
session count and session limit. The host value may not
include wildcards.
See the EXCEPTION
help for more information about session limiting and how to set session
limits specific to certain hosts and groups thereof.
SU
- Syntax:
- SU password
Allows access to functions which require Services
super-user privileges. Super-user privileges last until you quit IRC.
WARNING: If you enter an
incorrect password, Services will broadcast a warning message to all IRC
operators.
SET
- Syntax:
- SET option setting
Sets various global Services options. Option names
currently defined are:
- READONLY
- Set read-only or read-write mode
- DEBUG
- Activate or deactivate debug mode
SET READONLY
- Syntax:
- SET READONLY {ON | OFF}
Sets read-only mode on or off. In read-only mode, normal
users will not be allowed to modify any Services data, including channel
and nickname access lists, etc. IRCops with sufficient Services
privileges will be able to modify Services' AKILL list and drop or
forbid nicknames and channels, but any such changes will not be saved
unless read-only mode is deactivated before Services is terminated or
restarted.
This option is equivalent to the command-line option
-readonly.
SET DEBUG
- Syntax:
- SET DEBUG {ON | OFF | num}
Sets debug mode on or off. In debug mode, all data sent
to and from Services as well as a number of other debugging messages are
written to the log file. If num is given, debug mode is
activated, with the debugging level set to num.
This option is equivalent to the command-line option
-debug.
JUPE
- Syntax:
- JUPE server [reason]
Tells Services to jupiter a server -- that is, to create
a fake "server" connected to Services which prevents the real server of
that name from connecting. The jupe may be removed using a standard
SQUIT. If a reason is given, it is placed in the server information
field; otherwise, the server information field will contain the text "Jupitered
by nick", showing the nickname of the person who jupitered
the server.
UPDATE
- Syntax:
- UPDATE
Causes Services to update all database files as soon as
you send the command.
QUIT
- Syntax:
- QUIT
Causes Services to do an immediate shutdown; databases
are not saved. This command should not be used unless damage to
the in-memory copies of the databases is feared and they should not be
saved. For normal shutdowns, use the
SHUTDOWN
command.
SHUTDOWN
- Syntax:
- SHUTDOWN
Causes Services to save all databases and then shut
down.
RESTART
- Syntax:
- RESTART
Causes Services to save all databases and then restart
(i.e. exit and immediately re-run the executable).
REHASH
- Syntax:
- REHASH
Causes Services to re-read its configuration files and
update active settings. Some settings, cannot be changed with REHASH,
and will only take effect when Services is restarted; in these cases, a
message will be written to the Services log file, and a notice will be
sent notifying you of this.
If LoadModule
lines have been added to or removed from the main Services configuration
file (ircservices.conf), modules will be loaded or unloaded as
needed. Modules which no longer have a LoadModule line will be
unloaded in reverse order of loading; then, after the remaining modules
have been rehashed, new modules will be loaded in the order listed in
the configuration file. If an error occurs at any step, rehashing will
be aborted.
Note that due to module dependencies, some modules
cannot be removed or changed via REHASH; in such cases, you will need to
restart Services for the changes to take effect.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
Commands available to Services Super-Users only:
ADMIN
- Syntax:
- ADMIN ADD nick
ADMIN DEL nick
ADMIN LIST
Allows the Services super-user to add or remove
nicknames to or from the Services admin list. A user whose nickname is
on the Services admin list and who has identified to NickServ will be
able to access Services admin commands.
Any IRC operator may use the ADMIN LIST form of
the command. All other use limited to Services super-user.
RAW
- Syntax:
- RAW text
Sends a string of text directly to the server to which
Services is connected. This command has a very limited range of uses,
and can wreak havoc on a network or cause Services to crash if used
improperly. DO NOT USE THIS COMMAND unless you are absolutely
certain you know what you are doing!
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
ChanServ - Precede these
commands with /ChanServ [command] - For detailed syntax help, type
/ChanServ HELP [command] - Remember these are only the Oper level commands.
IRCop
LIST
- Syntax:
- LIST pattern
Lists all registered channels matching the given pattern.
Channels with the PRIVATE option set
will only be displayed to Services admins. Channels with the
NOEXPIRE option set will have a
! prepended to the channel name for Services admins.
If the FORBIDDEN, SUSPENDED or NOEXPIRE
options are given, only channels which, respectively, are forbidden, suspended
or have the NOEXPIRE flag set will be displayed. The options can be used in
any order and in any combination. These options are limited to Services
admins.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
Services Operator (SOP)
No additional commands available.
Services Administrators:
DROP
- Syntax:
- DROP channel
Unregisters the named channel. Can only be used by
channel founder, who must use the IDENTIFY
command first. (However, Services admins may drop any channel without
identifying for the channel.)
SET NOEXPIRE
- Syntax:
- SET channel NOEXPIRE {ON | OFF}
Sets whether the given channel will expire. Setting this
to ON prevents the channel from expiring.
INFO
- Syntax:
- INFO channel [ALL]
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.
Services admins can use the ALL parameter with
any channel.
GETPASS
- Syntax:
- GETPASS channel
Returns the password for the given channel. Note
that whenever this command is used, a message including the person who
issued the command and the channel it was used on will be logged and
sent out as a WALLOPS/GLOBOPS.
SUSPEND
- Syntax:
- SUSPEND [+expiry] channel reason
Prevents a channel from being used or identified for by
anyone. A channel can be unsuspended with the
UNSUSPEND command.
Unlike a forbidden channel, a
suspended one does not lose its information and will expire!
UNSUSPEND
- Syntax:
- UNSUSPEND channel
Allows users to use and identify for a previously
suspended channel.
FORBID
- Syntax:
- FORBID channel
Disallows anyone from registering or using the given
channel. May be cancelled by dropping the channel.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
NickServ - Precede these
commands with /NickServ [command] - For detailed syntax help, type
/NickServ HELP [command] - Remember these are only the Oper level commands.
IRCop:
LIST
- Syntax:
- LIST pattern [FORBIDDEN] [NOEXPIRE] [SUSPENDED] [NOAUTH]
Lists all registered nicknames for which either the nickname
itself or the last seen address (in user@host format) match the given
pattern. Nicks with the PRIVATE option
set will only be displayed to Services admins. For Services admins, nicks with
the
NOEXPIRE option set will have a !
prepended to the nickname, those that are suspended will be prepended by a *,
and those that have not yet been authorized (with the AUTH
command) will be prepended by a ?.
If the FORBIDDEN, SUSPENDED, NOEXPIRE, or
NOAUTH
options are given, only nicks which, respectively, are forbidden, suspended,
have the NOEXPIRE option set, or have not yet been authorized will be displayed.
The options can be used in any order and in any combination. These options are
limited to Services admins. (Note that the NOAUTH option is not available
unless the nickserv/mail-auth module is loaded.)
Examples:
- LIST joeuser@foo.com
- Lists all registered nicknames last used by
joeuser@foo.com.
- LIST *Bot*
- Lists all registered nicknames with Bot in their
names (case insensitive).
- LIST * NOEXPIRE
- Lists all registered nicknames which have been set to not
expire.
LISTEMAIL
- Syntax:
- LISTEMAIL pattern [FORBIDDEN] [NOEXPIRE] [SUSPENDED]
[NOAUTH]
Lists registered nicknames like the
LIST
command, but matches on E-mail addresses instead of user@host addresses. See the
LIST command help for more information.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
Services Operators:
No additional commands available.
Services Admins:
DROPNICK
- Syntax:
- DROPNICK nickname
Drops the given nickname from the NickServ database, as well
as any linked nicks.
UNLINK
- Syntax:
- UNLINK nick [FORCE]
Removes a link (alias) to your nickname created with the
LINK command. You cannot unlink the nick you are currently using;
change to another linked nick first before using this command.
Services admins may add the FORCE option, which
allows removal of a link to a nick other than their own.
LISTLINKS
- Syntax:
- LISTLINKS
Lists all nicks which are linked to your nick. The main nick
for the group of linked nicks will be indicated by a "*" to the left of
the nick.
Services admins may list links for any nick by specifying
the nick in the command.
ACCESS
- 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 achurch@*.dragonfire.net
- Allows access to user achurch from any machine in
the
dragonfire.net domain.
- ACCESS DEL achurch@*.dragonfire.net
- Reverses the previous command.
- ACCESS LIST
- Displays the current access list.
Services admins may give a nickname parameter to the LIST
command to display the access list for any nickname.
AJOIN
- Syntax:
- AJOIN ADD channel
AJOIN DEL channel
AJOIN LIST
Modifies or displays the autojoin list for your nick. This is
the list of channels that you would like to automatically join, and takes effect
whenever you identify to NickServ.
Services admins can list the autojoin list for any nickname
with the format
LIST nickname.
SET NOEXPIRE
- Syntax:
- SET [nickname] NOEXPIRE {ON | OFF}
Sets whether the given nickname will expire. Setting this to
ON
prevents the nickname from expiring. If no nickname is given, sets the no-expire
flag for your nick.
INFO
- 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.
Services admins may use the ALL parameter with any
nick.
LISTCHANS
- Syntax:
- LISTCHANS
Lists the names and the total number of channels you have
registered under your nickname.
Services admins may list channels for any nickname by
giving the nickname with the command (for example, /msg NickServ
LISTCHANS OtherNick).
GETPASS
- 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.
FORBID
- Syntax:
- FORBID nickname
Disallows a nickname from being registered or used by anyone.
May be cancelled by dropping the nick.
SUSPEND
- Syntax:
- SUSPEND [+expiry] nickname reason
Prevents a nickname, and all those nicknames with the same
root nickname, from being used or identified for by anyone. A nickname can be
unsuspended with the UNSUSPEND command.
Unlike a forbidden nickname, a suspended one does not lose its
information and will expire!
UNSUSPEND
- Syntax:
- UNSUSPEND nickname
Allows people to use and identify for a previously suspended
nickname.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
MemoServ - Precede these
commands with /MemoServ [command] - For detailed syntax help, type
/MemoServ HELP [command] - Remember these are only the Oper level commands.
IRCops:
No additional commands available.
Services Operators:
No additional commands available.
Services Admins:
SET LIMIT
- Syntax:
- SET LIMIT [nick | channel] {limit | NONE
| DEFAULT} [HARD]
Sets the maximum number of memos a nick (or channel) is
allowed to have. Setting the limit to 0 prevents the nick from receiving
any memos; setting it to NONE allows the nick to receive and keep
as many memos as they want; and setting it to DEFAULT restores
the limit to the default value (20 by default). If you do not give a
nickname or channel, your own limit is set.
Adding HARD prevents the user from changing the
limit. Not adding HARD has the opposite effect, allowing the user
to change the limit (even if a previous limit was set with HARD).
This use of the SET LIMIT
command is limited to Services admins. Other users may only enter a
limit for themselves or a channel on which they have such privileges,
may not remove their limit or set their limit to the default, may not
set a limit above the default limit, and may not set a hard limit.
INFO
- Syntax:
- INFO [nick | channel]
Without a parameter, displays information on the number
of memos you have, how many of them are unread, how many total memos you
can receive and when you are notified of new ones.
With a channel parameter, displays the same information
for the given channel.
With a nickname parameter, displays the same information
for the given nickname. This use limited to Services admins.
[ Top |
OperServ |
ChanServ |
NickServ | MemoServ ]
|
