Cannot use /os

The UnrealIRCd team does not officially provide support for any services packages that you may be using or want to use. This forum is provided so the community can help each other with services issues.

Moderator: Supporters

Locked
mao43
Posts: 14
Joined: Sat Feb 25, 2012 4:33 pm

Cannot use /os

Post by mao43 »

help why can't i use /os commands

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;
	};
};
still doesn't work
help!~~
Stealth
Head of Support
Posts: 2086
Joined: Tue Jun 15, 2004 8:50 pm
Location: Chino Hills, CA, US
Contact:

Re: Cannot use /os

Post 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.
katsklaw
Posts: 1124
Joined: Sun Apr 18, 2004 5:06 pm
Contact:

Re: Cannot use /os

Post 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.
mao43
Posts: 14
Joined: Sat Feb 25, 2012 4:33 pm

Re: Cannot use /os

Post 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
katsklaw
Posts: 1124
Joined: Sun Apr 18, 2004 5:06 pm
Contact:

Re: Cannot use /os

Post 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)
cards
Posts: 85
Joined: Sat Jun 12, 2004 5:04 am

Re: Cannot use /os

Post 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
NetAdmin
irc.420-HighTimes.com
katsklaw
Posts: 1124
Joined: Sun Apr 18, 2004 5:06 pm
Contact:

Re: Cannot use /os

Post 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.
Severus_Snape
Posts: 3
Joined: Tue Jan 10, 2012 10:39 pm
Location: Santiago, Chile

Re: Cannot use /os

Post by Severus_Snape »

Remember that you also must set up an Alias for /os to send it to operserv.
All your base are belong to us.
Locked