Page 1 of 1
op warn
Posted: Tue Jan 25, 2005 7:43 pm
by silent
Does anyone know what the options are for this directive,
set::options::fail-oper-warn;
I cant seem to find them in the documentation,
Thanx guys.
Posted: Tue Jan 25, 2005 7:47 pm
by Stealth
When fail-oper-warn is set, it notifies people who attempt to oper that the opers on the server have been notified.
Normally all the opers get the failed oper attempt notice, and the user trying to oper gets "No O-Lines for your host". When the option is set, the user attempting to oper gets an additional server notice saying the opers have been notified about the attempt.
Posted: Tue Jan 25, 2005 7:47 pm
by Syzop
Posted: Tue Jan 25, 2005 11:12 pm
by silent
I understand what the directive does, but I get an error when I put it into the config file.
set::options::fail-oper-warn;
Im unclear what the options are...
Posted: Wed Jan 26, 2005 12:39 am
by Stealth
There are no options. set::fail-oper-warn IS the option.
Posted: Wed Jan 26, 2005 1:33 am
by Syzop
I understand what the directive does, but I get an error when I put it into the config file.
set::options::fail-oper-warn;
That's the abreviated form
(as mentioned in the 3rd alinea of 4.36), you need to actually use a block, like:
Code: Select all
set {
options {
fail-oper-warn;
};
};
But you probably have a set::options already, so just put fail-oper-warn; in that.
Posted: Wed Jan 26, 2005 4:55 am
by aquanight
Wasn't that added in the CVS docs (which not everyone has
)?
Posted: Wed Jan 26, 2005 4:19 pm
by Syzop
I don't know, I thought of that, but... I'm spending too much time on supporting already, so I'm NOT going to check *grin* ;).
Posted: Wed Jan 26, 2005 9:08 pm
by Dukat
aquanight wrote:Wasn't that added in the CVS docs (which not everyone has
)?
Yes it was
Posted: Wed Jan 26, 2005 9:41 pm
by Syzop
What do you guys prefer that I do then?
1. Give a lot of support, doing 100% research and all, few coding
2. Give some limited support, lot more coding
3. Give no support at all, coding only
Coz I'm lost.. :)
I guess I should opt for 3, but from time to time I see horrible wrong answers here and then I hate it if people think it was right. Also, people tend to sometimes come up with problems (read: bugs) here, and don't report them on bugs.unrealircd.org :(.
That's the main reason I read these forums... But sometimes I get the bad-but-human urge to help people out, something which I probably should STOP! Because it means I spend like 30-60m less on coding ;P
I've managed to stop my support addiction @ #unreal-support, forums shouldn't be much harder! ;)
[of course I'll stay active on the spamfilter/release/website section]