Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Robin2130]

I have a problem with my services.
I want that 2 other persons have access by OperServ ex: (/os set superadmin on)

I have added the nicks in services.conf:

# ServicesRoot <nicks>  [REQUIRED]
#    Specifies the Services "super-users".  The super-users, or "roots" as in
#    Unix terminology, are the only users who can add or delete Services
#    admins.
#
#    You can specify more than one nick by separating each one by a space.
#
#    This is commented out by default; make sure you insert the correct
#    nick before uncommenting it.

ServicesRoot   "Robin2130 DJMO Kimahri"

But OperServ refused when the other persons attempt to have access on it.
I have restart the services eeveral times and I have rehashed my IRCD configuration.

Who have a solution?

Regalrds,

Robin

[Jobe]

Are the other users /oper'ed? and are they definatly identified?

[Edited on 9-7-2007 by Jobe1986]

[Robin2130]

Yes they are. They are also identifyed by Nickserv

[Jobe]

If they ARE /oper'ed AND identified to NickServ AND in ServicesRoot they WONT get Access denied.

So they dont match all 3 of those conditions.

Check they are identified using "/msg NickServ status NICK" If you dont get a 3, theyre not identified.

Check they are /oper'ed as a global oper or higher by simply /whois'ing them and checking that it says they are an operator (NOT a local operator).

And check they are detected as ServicesRoot by using "/msg OperServ staff" If they dont appear there with ROOT beside their name, theyre not in ServicesRoot in the correct services.conf.

[Robin2130]

Origineel gepost door Jobe1986
If they ARE /oper'ed AND identified to NickServ AND in ServicesRoot they WONT get Access denied.

So they dont match all 3 of those conditions.

Check they are identified using "/msg NickServ status NICK" If you dont get a 3, theyre not identified.

Check they are /oper'ed as a global oper or higher by simply /whois'ing them and checking that it says they are an operator (NOT a local operator).

And check they are detected as ServicesRoot by using "/msg OperServ staff" If they dont appear there with ROOT beside their name, theyre not in ServicesRoot in the correct services.conf.

They are identifyed by Nickserv en they are opered. and they don't are in the staff.

How can i fix this?

# ServicesRoot <nicks>  [REQUIRED]
#    Specifies the Services "super-users".  The super-users, or "roots" as in
#    Unix terminology, are the only users who can add or delete Services
#    admins.
#
#    You can specify more than one nick by separating each one by a space.
#
#    This is commented out by default; make sure you insert the correct
#    nick before uncommenting it.

ServicesRoot   "Robin2130 DJMO Kimahri"

This is okay right?

[bewerken aan 9-7-07 door Robin2130]

[katsklaw]

Robin, if you just added more Services Roots while Anope was running you need to restart Anope: /os restart

[Robin2130]

Origineel gepost door katsklaw
Robin, if you just added more Services Roots while Anope was running you need to restart Anope: /os restart

Yes i know, But it still don't work

[Jobe]

Then you didnt edit the CORRECT services.conf.

If youre running Anope on windows the default location is c:\program files\anope\data\services.conf

If on *nix the default location is ~/services/services.conf

If theyre not listed in /os staff AFTER a /os restart after editing servcies.conf then you either didnt edit the correct services.conf or the nicks arnt registered AND identified.

[Edited on 10-7-2007 by Jobe1986]