i already edited the services.conf
Code: Select all
ServicesRoot "Name"
and @ unrealircd.conf
Code: Select all
oper Name {
from {
userhost *@*;
};
class clients;
password "passy";
flags {
netadmin;
global;
};
};
help!~~
Moderator: Supporters
Code: Select all
ServicesRoot "Name"
Code: Select all
oper Name {
from {
userhost *@*;
};
class clients;
password "passy";
flags {
netadmin;
global;
};
};
Minor correction here. Some services packages require you to be an oper, Anope has an OSOpersOnly configuration setting that's enabled by default, Also by default, Atheme Services has a need_oper flag in place for oper type 'sra'. The above directive is from Anope 1.8 or older though.Stealth wrote:To use OperServ you need to be an oper in your services database and using a registered nick. OperServ does not care if you're an oper on your network or what access you have. Being an oper on your server and able to use OperServ are entirely different things.
Code: Select all
# OSOpersOnly [RECOMMENDED]
# If this is defined, only IRC Operators will be permitted to use
# OperServ, regardless of module based command access restrictions.
OSOpersOnly
If you read his/her first post you would discover (s)he is a ServicesRoot by his/her own admission.cards wrote:YOu also need to be in the services access list. This mean you are either:
a) A Services root (Defined in the services.conf file)
b) A Services Admin (for anope /os admin add <nick>) <<< MUST BE DONE BY A ROOT USER
c) A Services Oper (for anope /os oper add <nick>) Must be done by a SA or Root