ROOT

Many of the OperServ commands are listed in the OperServ help files however they are issued with different services agents such as NickServ or ChanServ, the reason why they are listed under OperServ is because you need OperServ access to issue these commands. OperServ access levels are Services Administrator also referred to as SA, ChanServ Super Op aka CSop, and root administrator.

@SHUTDOWN - Will Shut down services.

@UPDATEDB - Will update Nick, Chan, and OperServ Database.

AOP - Modify AOP lists for any room.

AUTOKILL - Set permanent akills on large domains.

FORBID - Prevent registration of certain nicks or rooms.

HELP - Get help on root commands.

JUPE - Prevent servers from connecting to the network.

KEEP - Prevent a nickname or room from expiring.

LOCKPASS - Stop a password from being viewed by CSops.

OPER - Accessing Operator Prviliges through OperServ.

OPERCFG - Network operator configuration additions and changes.

PROTECT - Make a room be protected by network services.

SENDMEMO - Send a memo to all registered nicknames or to all room founders.

SOP - Modify SOP lists for any room.

UOP - Modify UOP lists for any room.

VOP - Modify VOP lists for any room

Example:

/os help root <topic>

Usage: AOP <room> [ADD|DEL|LIST|WIPE] [<nick|number>]

Root admins can add, delete, or wipe an aop in a room's list without being in the SOP list. A root adding an AOP will override NOOP, so you can op people whether they wish it or not. You also can add their ops immediately, without them needing to accept it. Note: There is a limit of 250 users that can be added to anAOP list.

ADD - Add a user to a room's AOP list.

DEL - Remove a user from a room's AOP list.

LIST - List the AOP list entries.

WIPE - Remove all entries from a room's AOP list.

Examples:
 
/msg chanserv aop #downtown ADD web

/msg chanserv aop #downtown DEL 2

/msg chanserv aop #downtown LIST

/msg chanserv aop #downtown WIPE

This gives you the ability to help any room with their AOP list. Sometimes it is easier to just fix things for someone rather than explain how they can do it for themselves. Since the ops will be added without needing to consent, you can temporarily delete them and then add them back without much inconvenience. 
Also, if your network has any requirements that the room is not meeting, you can enforce them. You will probably not need to use these commands, since the SOPs for the room should be able to manage their own lists, and it is unlikely for problems to arise. But in case you ever need the ability, you have it.

Usage: AUTOKILL [ADD|DEL] <hostmask> [<reason>] [<time>] [FORCEADD]

This command will add or delete an autokill from services. The format of an AUTOKILL is ident@host. Roots can place akills that affect more than 20% of the users on the network. If you do not specify a time the autokill will be removed within 30 minutes by services. Only CSops and roots can place permanent autokills in the format ident@host reason PERM.

Roots can only autokill more than 55% of the network if the FORCEADD argument is added as the very last line of the autokill. If the forceadd argument is not added and the autokill would affect more than 55% of the network's users, services will not add the autokill.

Examples:
 
/msg operserv autokill mirc@*.com clones 45 FORCEADD

/msg operserv autokill pirch@*.hostmask.org spamming 60

It is unlikely that you will ever have a reason to autokill such a large percentage of your network. These safeguards are designed to keep you from doing so by accident. But if you have a reason to do so, the option is available. You should be careful that your autokill does not also affect you.

Usage: FORBID [ADD|DEL|LIST|WIPE] <nick|room>

This command is used to prevent registration of any nickname or room matching the specified nickname or room. It will not prevent you from creating the room or using the nickname. It will simply not allow registration of that nickname or room.

ADD - Prevent registation of a nick or room
DEL - Allow registration of a nick or room that had been forbidden.

LIST - List the nicks and rooms that may not be registered.

WIPE - Remove all entries from the forbid list

Examples:
 
/msg operserv forbid add Web reserved nickname

/msg operserv forbid add #room cannot be registered

You should forbid nicks if you intend to hold them for someone who is not currently chatting. Then people can use the nick but it won't be owned by anyone. Then when the person the nick is held for begins chatting you can remove the forbid while they are using it. 
Rooms should be forbidden if the room name is constantly causing problems. If a room has been closed multiple times and it keeps being registered by people who do not run it well, it may be best to just forbid it from being owned.

Usage: HELP ROOTS [<command>]

This command is used to get more help on a particular topic.

Examples:
 
/msg operserv help roots

/msg operserv help roots forbid

The built in references are good for checking syntax, the exact name of a command, or learning what a command does. You will probably want to use the online help as your first resource when you encounter difficulties.

Usage: PROTECT <room> <on|off>

This command will make a room protected by services. No one will be able to do a getpass or setpass on the room. You will not be able to join the room unless you are on the aop/sop list. The founder is automatically services.

Example:

/msg chanserv protect #root on

This can be useful for network rooms, such as administrative rooms. You do not really need anyone in charge of the room, and this way you do not need to worry about administrative changes. However, while the room is protected, you cannot add AOPs and SOPs. 
When you turn internal off, it reverts back to the original founder. Although roots can still add AOPs and SOPs or change the foundership. Then when done modifying the lists, the room can be set back to being internal.

Usage: JUPE [ADD|DEL|LIST|WIPE] <server> [<reason>]

The jupe command allows you to create a 'pseudo-server' connected under services, this prevents the actual server from connect ingto the network. You cannot SQUIT a juped server. It can only be removed by using the JUPE DEL command..

ADD - Add a jupe for a server.

DEL - Delete a jupe for a server.

LIST - List all current jupes.

WIPE - Remove all jupes.

Examples:
 
/msg operserv jupe add irc.server.com Administrative Decision

/msg operserv jupe del irc.server.com

Juping a server is an emergency measure when a server is causing the network problems or the people running the server have become a security threat. Juping a server keeps it off of your network. If this is a temporary measure just leave the jupe until you are ready to have it reconnect. 
If this is to be a permanent measure you should delete that server's entry so that it is no longer configured to be connected to your network. If you do jupe a server, you should generally inform the person in charge of that server as soon as possible.

Usage: KEEP <nick|room> [on|off]

This command prevents a nick or room from ever expiring from lack of use. However, a room will expire even with keep on if the founder's nick expires or is dropped. If you wish to keep a room, set keep on for the room and the founder's nickname.

Example:

/msg nickserv keep Lashe|| on

/msg chanserv keep #downtown on

This is useful for any official room on your network. It is also useful for your own nicks and the nicks of other people who help to run the network. Official nicknames should be protected because they may become recognized and trusted. These nicks should only be used by their owners to prevent others from abusing that trust.

Usage: LOCKPASS <nick|room> [on|off]

This will lock a nick or room password. Only roots will be able to GETPASS a nickname or room that has a locked password, and they will have to remove the lock first.

Examples:
 
/msg nickserv lockpass JoshM on

/msg chanserv lockpass #downtown on

This is an extra security measure that roots can take to protect their passwords. Ideally, you should trust everyone you have given CSop access to, but extra security does not hurt. If a CSop attempts to getpass a locked nick, the owner of the nick will be sent a memo stating who attempted to getpass it. You can also lockpass official rooms. You should not need the password often.

Usage: OPER <nick> <password>

This command allows a user with appropriate privileges to gain operator access from any server.

Examples:

/os oper Mark M1PasS

This command allows you to centrally manage users with operator access.

Usage: OPERCFG [<nick>] <command> [<value>]

The oper command will allow you to add, delete, disable or modify flags on an operator or
add/del an SA, CSop or root.

ADD - Add an operator.
DEL - Delete an operator.
DISABLE - Disable an operators access.
ENABLE - Enable an operators access.
FLAGS - List, add or delete flags on an operator.
LIST - List an operator's access flags.
LISTADM - List all the people with OperServ access.
PASSWORD - Changes your password.

Examples:
/os help root opercfg

When you add an oper /os opercfg nick add oper pass... and later on you want to promote the person to csop, you need to delete the oper and add the command again with csop.

Usage: OPERCFG <nick> ADD <flag> <password>

This will add a 'registered' user enabling them to get operator and services privileges on the network. The following are the default flags that can be entered. Specific permissions can be edited using the FLAG command.

Helper - Is able to see help requests by users.

Oper - Commands that deal with server operations.

SA - Services Administrators have access to commands that allow certain interactions with channels and their settings.

CSOP - Channel Service Operators have extensive channel and user capabilities.

Root - Full access to all command levels.

Examples:

/os opercfg Mark add csop M1pasS

/os opercfg Mark add csop

If this command is specified with a password then they can remotely identify from any server on the network. If the password is ommited then they must gain access from a local operator configuration and then they can access their services permissions.

Usage: OPERCFG <nick> DEL

Deletes the specified Operator configuration.

Examples:

/os opercfg Mark del

Used to specifically delete an operator configuration. If this is temporary you can DISABLE the configuration which will allow you to keep the settings but deny access until it's re-enabled.

Usage: OPERCFG <nick> DISABLE

Disables the specified Operators remote access ability.

Examples:

/os opercfg Mark disable

In some cases you may wish to remove an operators ability to use the remote access fucntions but not delete the profile. If you do want to remove the profile permanently you can use the DELETE command. You can restore access with the ENABLE command.

Usage: OPERCFG <nick> ENABLE

Enables a profile that has been previously disabled.

Examples:

/os opercfg Mark enable

If you have used the DISABLE command to remove access to a specific operator the use of this command will restore all privilges.

Usage: OPERCFG <nick> <flag> [<ADD|DELETE>]

When you add an operator configuration at a specified level (helper, oper, sa, csop, root) there are a number of commands that come with that access level. The flag command lets you get very specific about what each operator can or cannot do. This gives you very complete control over your environment.

AKILL - Place a network wide ban on a user@host address.

CDROP - Drop registered channels without being the founder.

CPASSWD - Modify channel passwords, and to mark channels.

CCLOSE - Close and reopen channels.

CFORCEREG - Register channels without having operator status in them.

CWIPE - Wipe ChanServ access lists without owning the nickname.

FREEZE - Suspend nicknames and channels.

GLOBAL - Send notices to all the users on the network.

HELPER - Receive Helpop notices.

IGNORE - Modify the services ignore list.

MASSDEOP - Remove operator status from all users in a channel.

MASSKICK - Remove all users from a channel.

NDROP - Drop registered nicknames without being the owner.

NPASSWD - Modify nickname passwords, and to mark nicknames.

NWIPE - Wipe NickServ access lists without owning the nickname.

SQLINE - Modify the services qline list.

TRIGGER - Modify the clone detection threshold for a host or user@host address.

Examples:

/os opercfg Mark akill del

Used in conjunction with the PRIVILEGE command set this will give you very finite control over the commands that all users have access to. To get a complete list of the commands a specific Operator has access to, use the LIST command.

Usage: OPERCFG <nick> LIST

Lists all flags for the specified operator.

Examples:

/os opercfg Mark list

For a list of all the flags that are on the system see the a FLAG command.

Usage: OPERCFG LISTADM

Lists all currently configured operators by access level.

Examples:

/os opercfg listadm

The general list command is used to determine who does and does not have specific levels of access. Use the LIST command for specific operator configurations.

Usage: OPERCFG <nick> PASSWORD <oldpass> <newpass>

This command is used to change the remote access password to a Operator profile.

Operators may use this command to change their own passwords. To change a password you must use the old password that you're changing plus the new password that you want installed. Root users may change the password by just using the new password.

Examples:

Operator changing their password: /os opercfg Mark password M1pasS% N3wPa55

Root user changing configuration password: /os opercfg Mark password N3wPa55

Passwords can be added when you are creating an Operator configuration, see the ADD command for more information.

Usage: PROTECT <room> <on|off>

This command will make a room protected by services. No one will be able to do a getpass or setpass on the room. You will not be able to join the room unless you are on the aop/sop list. The founder is automatically services.

Example:

/msg chanserv protect #root on

This can be useful for network rooms, such as administrative rooms. You do not really need anyone in charge of the room, and this way you do not need to worry about administrative changes. However, while the room is protected, you cannot add AOPs and SOPs. 
When you turn internal off, it reverts back to the original founder. Although roots can still add AOPs and SOPs or change the foundership. Then when done modifying the lists, the room can be set back to being internal.

Usage: SENDMEMO [NICKNAMES|FOUNDERS] <message>

Root admins can send a global memo on the server or network to all the registered nicknames or to all the people who have a registered room.

Examples:
 
/msg operserv sendmemo founders All room owners.

/msg operserv sendmemo nicknames To all the users with a registered nickname.

This is a good way to send important information. If you are making any policy changes this can be used to announce them. If you have a large number of users having problems with something, you can send helpful information to educate them. 
For example, if you were to change the expiry time, you should probably memo your user base so they would know. However, memos are not a completely reliable way to send information, since some people may not read their memos.

Usage: @SHUTDOWN <reason>

This command will shut down services. First it will flush the database to disk. The command /servstart will restart services.

Example:

/msg operserv @shutdown Services will be back shortly.

You can bring services back up by connecting to the server that holds services. Or you can restart your server with /restart and it will restart with services connected, but this will toss everyone off the server while it restarts, and cause splits if there are other servers linked to yours. The easiest way to get services back is probably the /servstart command. 
See servstart in the Services Administrators Server Commands section.

Usage: SOP <room> [ADD|DEL|LIST|WIPE] [<nick|number>]

Root admins can add, delete, or wipe an SOP from a room's list without having any access to that room. Note: There is a limit of 250 users that can be added to a room's SOP list.

ADD - Add a user to the SOP list.

DEL - Remove a user from the SOP list.

LIST - List all the SOP list entries.

WIPE - Clear the SOP list of all entries.

Examples:
 
/msg chanserv sop #downtown add web

/msg chanserv sop #downtown del 2

/msg chanserv sop #downtown list

/msg chanserv sop #downtown wipe

This command allows you to fix any problems that might arise in an SOP list for any room. It works much as the AOP command does, except it is for the SOP list. Please see AOP.

Usage: UOP <room> [ADD|DEL|LIST|WIPE] [<nick|number>]

Root admins can add, delete, or list a UOP to any room's list without being on the SOP list. Note: There is a limit of 250 users that can be added to a room's UOP list.

ADD - Add a user to the UOP list.

DEL - Remove a user from the UOP list.

LIST - List all the UOP list entries.

WIPE - Clear the UOP list of all entries

Examples:
 
/msg chanserv uop #downtown add web

/msg chanserv uop #downtown del 2

/msg chanserv uop #downtown list

/msg chanserv uop #downtown wipe

This command allows you to fix any problems that might arise with a UOP list for any room. It works much as the AOP command does, except it is for the UOP list. Please see AOP.

Usage: @UPDATEDB

Forces services to flush its database to disk. By default services saves its databases on a 30 minute rotating schedule.

Example:

/msg operserv @updatedb

Use this if you need to save the database. For example, if you are worried about a potential system crash or you want to shut down the network temporarily. But usually the automatic database saves will be sufficient.

Usage: USERINFO <nick>

This command will give out the identifier on a user, which rooms the user is in, and the flags for that user. It will also show you the server he/she is using, the real name field information, the hostmask and flood credit.

Example:

/msg operserv userinfo Mark

This can be used if you need to see where a user is, or just want to get as much information as you can. But generally you will not need to check the userinfo on people.

Usage: VOP <room> [ADD|DEL|LIST|WIPE] [<nick|number>]

Root admins can add, delete, or list VOPs to a room's list without being on the SOP list. Note: There is a limit of 250 users that can be added to a room's VOP list.

ADD - Add a user to the VOP list.

DEL - Remove a user from the VOP list.

LIST - List all the VOP list entries.

WIPE - Clear the VOP list of all entries.

Examples:
 
/msg chanserv vop #downtown add web

/msg chanserv vop #downtown del 2

/msg chanserv vop #downtown list

/msg chanserv vop #downtown wipe

This is much like the AOP command, except for the VOP list. Please see AOP.