AKILL

    Usage: AKILL <add|del|[-]> <hostmask> [<reason>] [<time>]

    This command will add, list or delete an autokill from services. The format of an akill is ident@host. However, if your akill affects more than 20% of the users on the network, you will need to ask a root to place the akill for you. If you do not specify a time the akill will be removed within 30 minutes by services. Only Csops and Roots can place permanent akills. The format for a permanent akill is ident@host reason PERM.

    Examples:
    /msg operserv akill pirch@*.oricom.ca spamming 60
    /msg operserv akill *@home.oricom.ca spam PERM
    /msg operserv akill -pirch@*.oricom.ca
    /msg operserv akill add pirch@123.213.123.* clones 15
    /msg operserv akill del pirch@*.oricom.ca
    /msg operserv akill list
    /msg operserv akill wipe

    Akills are network bans. They will prevent anyone who matches their description from joining the chat network. They should be added as necessary to ban users who have been causing problems, but in almost all cases they will also ban innocent people from the same service provider. This is why most bans should be temporary. People who cause serious problems should be reported to their service providers with logs explaining what they have been doing.


    AUTOKILL

    This command is identical to akill except for some abilities that roots have when using AUTOKILL that do not work with AKILL. This allows roots to use AKILL in general and AUTOKILL when they want to set larger bans.

    See AKILL


    CHANSERV

    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.

    CLOSE - Prevent a room from being used, it will expire normally.
    DROP - Drop a registered room.
    FTRANSFER - Transfer ownership of a registered room to a specified nick.
    GETPASS - Show the password for a registered room .
    INFO - Show info on a registered room.
    LIST - Show rooms that match a selected value.
    MARK - Set a room so that it can't be getpassed or setpassed.
    REGISTER - Register a room without being an op on it.
    REOPEN - Reverse the close command so the room can be used.
    SETPASS - Set the password for a registered room.
    UNIDENTIFY - Make chanserv forget your identification for a room.
    WIPE - Delete all entries to a list for a room.

    Example:
    /msg operserv help chanserv close


    IDENTIFY

    Usage: IDENTIFY <nick> <nick|room> <pass>

    This command remotely identifies a user without giving the user the password. The user will show as being identified to the room or nickname.

    Examples:
    /msg operserv identify joeuser nikb Froxilanthi
    /msg operserv identify nikb #webchat webPass

    If you wish to give a nick or room to a user this is a good way to do so. You might not want the user to know the password, since some people reuse passwords for multiple things. But this way they can be seen as fully identified and can change the password without ever being told the original password. This command should only be used when you are willing to give someone the nick or room you are giivng them access to.

    See also FTRANSFER


    IGNORE

    Usage: IGNORE [ADD|DEL|LIST|WIPE] [<entry>] [<reason>]

    Services has an ignore list which functions similarly to the way a user can ignore another user. If a user matches a mask in the ignore list and attempts to use services, he or she will not get a reply. Ignores do not affect IRC operators.

    ADD - Add someone to the ignore list.
    DEL - Remove someone from the ignore list.
    LIST - List all the entries in the ignore list.
    WIPE - Remove all of the entries from the ignore list.

    Examples:
    /msg operserv ignore add *!myident@*.webmaster.com services flooding
    /msg operserv ignore add Tim!*@* constant services abuse
    /msg operserv ignore del Tim!*@*
    /msg operserv ignore list
    /msg operserv ignore WIPE

    Ignores are another way to deal with users who cause problems. It is not quite as harsh as an autokill, because the person can still chat. Yet, it is more confusing to the users affected. If the ignore is kept for a long time then affected users, being unable to identify for nicks or rooms, will lose anything they have registered with services. Since ignores are not set with times, you should keep track of which ignores you set and periodically clean out the ignore list.


    LISTADM

    Usage: LISTADM

    This command will give you the nicknames of the network operators that have access to OperServ. Services Admins and CSOPs are listed together. Root admins are listed separately.

    Example:
    /msg operserv listadm

    This command is useful if you are unsure who has what level of access, or if you need to find a root admin.


    MASSDEOP

    Usage: MASSDEOP <room>

    The massdeop command allows you to remove operator status in the specified room for all users. If you are in the room, you will also be deopped.

    Example:
    /msg operserv massdeop #opers

    Massdeop is a quick way to try to restore order in a room if people have been opped who should not be. Once all the people are deopped in the room, you can start reopping those who should be opped. AOPs and higher will be able to op themselves with chanserv.


    MASSKICK

    Usage: MASSKICK <room> [<reason>]

    The masskick command allows you to completely empty a room. Everyone, including the person who issued the command if he or she is in the room, will be kicked out. Note: To prevent people from automatically rejoining, ChanServ will join the channel for 2 minutes to enforce a ban of *!*@*.

    Example:
    /msg operserv masskick #webchat abuse

    This command is useful to empty a room that has violated network rules. For example, if a room has been advertising itself in annoying ways, a masskick may cause the founder and the channel operators to reconsider their behavior.


    MEMOSERV

    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.

    WIPE - Delete all entries in a nick's memoserv ignore list

    Example:
    /os help memoserv wipe


    NICKSERV

    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.

    DROP - Drop a registered nick.
    INFO - Show info on a registered nick.
    GETPASS - Show the password for a registered nick.
    LIST - List nicknames that match a selected value.
    MARK - Set a nickname so that it can't be getpassed or setpassed.
    SETPASS - Set the password for a registered nick.
    UNIDENTIFY - Make nickserv forget your identification to a nickname.
    WIPE - Delete all access list entries for a registered nick.

    Example:
    /msg nickserv getpass Mark


    QLINE

    Usage: QLINE [ADD|DEL|LIST|WIPE] [<nick>] [<reason>]

    Using this command will add a global Qline. A Qline is a nickname that is prohibited on the server or network. Network Operators may use qlined nicks, but regular users cannot. Services will prevent the use of a nickname on the network, unlike the /qline command which is specific to a server.

    ADD - Add a QLINE on the network.
    DEL - Delete a QLINE on the network.
    LIST - List the QLINE entries.
    WIPE - Remove all QLINES

    Examples:
    /msg operserv qline add oper security
    /msg operserv qline del spider
    /msg operserv qline list
    /msg operserv qline wipe

    Qlines should be used to ban nicknames that are either offensive or misleading. Nicks such as "Operator" or "CSop" may be qlined so that normal users do not think that people using those nicks actually are authorities that must be listened to. Other nicks can be prohibited to mirror the profanity filters. Operators can use prohibited nicknames because they are expected to be trustworthy and familiar with when it is appropriate to use such nicks.


    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>


    SPECS

    Usage: SPECS

    This command will allow you to list your own access to services on NickServ ChanServ and OperServ, flags will be listed by what they do. You must be identified to NickServ in order to view your own flags.

    Example:
    /msg operserv specs

    This is a useful command if you are having difficulty getting another command to work. Even if you normally have access, perhaps you are using the wrong nick or failed to identify. The specs command will explain what access you have, so you can make sure that you should be able to issue the commands you want.


    TRIGGER

    Usage: TRIGGER [ADD|DEL|LIST|WIPE] <value> [<host>]

    This will set the trigger level for a host. The trigger level determines how many people from the same host are needed to set off a clone alert. To add a permanent trigger level, use the parameter add To add a temporary trigger level on a host do not use add. A temporary trigger lasts for as long as there is someone matching the trigger online. Note, that if a both a PERM and a TEMP trigger are in effect, the TEMP trigger takes precedence, but once the hostcount reaches zero, it is lost. Only Operators with the 'TRIGGER' flag may use this command

    ADD - Add a permanent trigger.
    DEL - Delete a trigger.
    LIST - List the current triggers.
    WIPE - Remove all triggers

    Examples:
    /os trigger wipe
    /os trigger add 15 123.123.123.123 50 cybecafe
    /os trigger list
    /os trigger del 123.123.123.123

    Triggers help to keep clone alerts useful. People who are causing problems can be given specific triggers to alert you faster, and hosts that are accidentally setting off clone alerts can be adjusted higher. Clone alerts should always be investigated to determine if they are actually caused by malicious bots. But with time as the triggers become customized, the clone alerts will become more and more accurate.


    UPTIME

    Usage: UPTIME

    This command will give you the services uptime, the number of people currently online, the maximum number that have been online, and the number of registered rooms and nicknames on the network.

    Example:
    /msg operserv uptime

    This command merely gives information, it does not affect anything. It is good for seeing how your server and network have been doing.