Hi David!

Am 28.12.2012 um 21:19 schrieb David Woodfall dave@dawoodfall.net:

I seem to be having problems with certain modules in Atheme, which are connected to XOP. Is there anything I need to set in the ngircd.conf to turn on XOP?

[28/12/2012 17:58:48] atheme 7.0.5 is starting up... [28/12/2012 17:58:48] Module chanserv/owner requires owner support, refusing to load. [28/12/2012 17:58:48] module_load(): module /usr/modules/chanserv/owner init failed [28/12/2012 17:58:48] Module chanserv/protect requires protect support, refusing to load. [28/12/2012 17:58:48] module_load(): module /usr/modules/chanserv/protect init failed [28/12/2012 17:58:48] Module chanserv/quiet requires a ban-like mode +q, refusing to load. [28/12/2012 17:58:48] module_load(): module /usr/modules/chanserv/quiet init failed [28/12/2012 17:58:48] module_load(): module /usr/modules/groupserv/main is already loaded [at 0x15dd3e0] [28/12/2012 17:58:48] opensex: data format version is 11. [28/12/2012 17:58:48] groupserv: opensex data schema version is 4. [28/12/2012 17:58:48] pid 10970 [28/12/2012 17:58:48] running in background mode from /usr

As you can see from the output, it Atheme thinks that ngircd doesn't support owner, protect or quiet, which according to the changelog was added to ngircd around 20rc1

Right, ngIRCd supports XOP modes starting with release 20. But most probably the Atheme protocol module is older and not aware of these new modes …

Probably pinging the Atheme developers helps?

Regards Alex