Anope IRC Services

Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Tommy Hermans on March 07, 2014, 01:18:23 PM

Title: Services admin
Post by: Tommy Hermans on March 07, 2014, 01:18:23 PM

Hello,

i have a problem defining my anope services admin.

I have added in services.conf the following line:

Code: [Select]

ServicesRoot   "Tommy[admin]"
Also changed:

Code: [Select]

#OSOpersOnlyWith the # in front of it.

The nickname is also registered, but i still have no powers to user operserv, botserv, etc. commands
Everytime i try i get Permission Denied error.

Can anybody tell me what i do wrong.
I restarted the process offcourse after changing the conf file.

Everything works perfectly, chanserv and nickserv are running without problems, only the services admin commands can not be used.
How can i set my admin nickname Tommy[admin] as a services admin.

Thank you for your support and i hope anybody can help me with this.

Kind regards,
Tommy

Title: Re: Services admin
Post by: Tommy Hermans on March 07, 2014, 01:54:45 PM

I don't know if it means anything but when i use th /whois command on my admin nick, i see the text:
Tommy[admin] is available for help

I don't see this when i whois other users.

But still i get access denied when i want to use operserv or botserv commands.

Strange problem i think.

Edit:

This is what i see with /ns info Tommy[admin] all:
[15:28:42] [NOTICE NickServ]: Tommy[admin] is tommy
[15:28:42] [NOTICE NickServ]: Tommy[admin] is a services root administrator.
[15:28:42] [NOTICE NickServ]: Tommy[admin] is currently online.

But when i try to use operserv, this is wat i see:
[15:31:07] -OperServ- Access denied.

trying to access operserv with services root administrator account does not work, maybe you have any idea in this?

Title: Re: Services admin
Post by: katsklaw on March 07, 2014, 03:36:09 PM

Type: /msg operserv staff

If you have a * next to your nick, then you should have access. You must be identified as the root user and using the root users nick as well. I know you disable OSOpersOnly but make sure you have /oper'ed anyway.

Title: Re: Services admin
Post by: Tommy Hermans on March 07, 2014, 04:21:00 PM

Thank you for the help, as far as we now are we do have root access as services admin.
Also we can use some commands of operserv and botserv.

But i can not give superadmin on status with operserv, or create new bots with botserv.
Do i need to install any module or anything about that?

I don't have all the powers at this time to use all the commands, even while we are on the staff list with a * next to our name.

I have searched for modules or any kind of explanation but didn't find any, maybe you could tell me how to active/use this?

Title: Re: Services admin
Post by: katsklaw on March 07, 2014, 08:13:55 PM

SuperAdmin requires the SuperAdmin directive to be enabled in services.conf and it needs to be activated on IRC too. /msg operserv help set superadmin. The setting of SuperAdmin is not automatic nor persistent. Please read /msg operserv help completely. Most of your answers are found in the documentation either in the docs directory, via /msg *Serv help or online https://wiki.anope.org/index.php/Main_Page

/msg botserv help add
/msg botserv help assign

Title: Re: Services admin
Post by: Tommy Hermans on March 09, 2014, 01:56:32 PM

Hello,

It took some time to figure everything out, but i finally got everything working.

So thank you very much for your support and answers, we are now full server and irc operators, so we can now use full access permissions.

This topic may close now, and again thank you for the help and support.