Page 1 of 1
Cannot use /os
Posted: Sat Feb 25, 2012 8:41 pm
by mao43
help why can't i use /os commands
i already edited the services.conf
'
and @ unrealircd.conf
Code: Select all
oper Name {
from {
userhost *@*;
};
class clients;
password "passy";
flags {
netadmin;
global;
};
};
still doesn't work
help!~~
Re: Cannot use /os
Posted: Sat Feb 25, 2012 10:35 pm
by Stealth
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.
Re: Cannot use /os
Posted: Sat Feb 25, 2012 11:40 pm
by katsklaw
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.
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.
To gain OS access you need to:
1> Be an IRCop (Services generally don't care if you are a server admin or netadmin, just be umode +o)
2> You have to be USING and IDENTIFY'ed to a REGISTERED nick that is allowed OS access.
Anope also requires you to be an IRCop, umode +o, to register any ServicesRoot nick. While oper access and services access are indeed 2 different things as Stealth pointed out, Anope requires you to be one before you get the other.
Hope that helps.
Re: Cannot use /os
Posted: Sun Feb 26, 2012 2:26 am
by mao43
mine is this
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
what do i need to put there?
and im registered and identified nick
how can i umode +o??
my user current mode is [04:37.12] * Your mode is now +i
im using Anope-1.8.7
Re: Cannot use /os
Posted: Sun Feb 26, 2012 2:48 am
by katsklaw
umode +o comes from issuing the /oper command
1> /oper
2> identify
3> try /os staff (if your nick has a * next to it, then you can use OS commands)
Re: Cannot use /os
Posted: Mon Feb 27, 2012 4:32 am
by cards
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
Re: Cannot use /os
Posted: Tue Feb 28, 2012 1:28 am
by katsklaw
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
If you read his/her first post you would discover (s)he is a ServicesRoot by his/her own admission.
Re: Cannot use /os
Posted: Sat Mar 10, 2012 3:07 pm
by Severus_Snape
Remember that you also must set up an Alias for /os to send it to operserv.