summaryrefslogtreecommitdiff
path: root/data
diff options
context:
space:
mode:
Diffstat (limited to 'data')
-rw-r--r--data/example.conf9
-rw-r--r--data/operserv.example.conf15
2 files changed, 6 insertions, 18 deletions
diff --git a/data/example.conf b/data/example.conf
index 53fceecf4..8e271dc87 100644
--- a/data/example.conf
+++ b/data/example.conf
@@ -667,13 +667,13 @@ log
* pesudo-serv/commandname (eg, operserv/akill, chanserv/set)
*
* Valid server options are:
- * connect, quit, sync
+ * connect, quit, sync, squit
*
* Valid channel options are:
* create, destroy, join, part, kick, leave, mode
*
* Valid user options are:
- * connect, disconnect, quit, nick, ident, host, mode, maxusers
+ * connect, disconnect, quit, nick, ident, host, mode, maxusers, oper
*
* Rawio and debug are simple yes/no answers, there are no types for them.
*
@@ -696,7 +696,10 @@ log
log
{
target = "globops"
- admin = "global/* operserv/mode operserv/kick operserv/akill operserv/s*line operserv/noop operserv/jupe */forbid nickserv/getpass */drop"
+ admin = "global/* operserv/mode operserv/kick operserv/akill operserv/s*line operserv/noop operserv/jupe operserv/oline operserv/set operserv/svsnick nickserv/getpass */drop"
+ servers = "squit"
+ users = "oper"
+ other = "expire/* bados akill/*"
}
/*
diff --git a/data/operserv.example.conf b/data/operserv.example.conf
index dbedb69e6..08410eb1c 100644
--- a/data/operserv.example.conf
+++ b/data/operserv.example.conf
@@ -111,21 +111,6 @@ operserv
#killonsqline = yes
/*
- * Defines what actions should trigger notifications. The list must be separated by spaces.
- *
- * The notifications are:
- * - oper: A user has become an IRC operator
- * - bados: A non-IRCop attempts to use OperServ
- * - akillexpire: An AKILL has expired
- * - snlineexpire: An SNLINE has expired
- * - sqlineexpire: An SQLINE has expired
- * - exceptionexpire: A session exception has expired
- *
- * This directive is optional, if left blank, there will be no notifications.
- */
- notifications = "oper"
-
- /*
* Enables session limiting. Session limiting prevents users from connecting more than a certain
* number of times from the same host at the same time - thus preventing most types of cloning.
* Once a host reaches it's session limit, all clients attempting to connect from that host will