Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Anope disconnected (charybdis 3.3.0)  (Read 4895 times)

0 Members and 1 Guest are viewing this topic.

Mr. X

  • Anope User
  • Offline Offline
  • Posts: 3
Anope disconnected (charybdis 3.3.0)
« on: June 01, 2012, 02:30:43 AM »

when i added a bot with botserv
Code: [Select]
/msg botserv bot add TortuBOT tbot IRCTortuga/bot Tortu Bot
i recived a notification :
Code: [Select]
-OperServ- OPERWALL - TortuBOT is now an IRC operator.and anope was disconnected from the server:
Code: [Select]
* *** Notice -- Netsplit irc.servidortortuga.com.ar <-> servicios.tortuga (1S 7C) (Invalid UID AAAAAG for nick TortuBOT on servicios.tortuga)
* *** Notice -- servicios.tortuga was connected for 974 seconds.  3/18 sendK/recvK.

i tryed again, and now rund!

what it was?  :-\

(sorry for my bad english   :P )
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: Anope disconnected (charybdis 3.3.0)
« Reply #1 on: June 01, 2012, 02:32:23 AM »

1.9 doesn't support charybdis, how are you linking it?
Logged

Mr. X

  • Anope User
  • Offline Offline
  • Posts: 3
Re: Anope disconnected (charybdis 3.3.0)
« Reply #2 on: June 01, 2012, 02:35:38 AM »

Code: [Select]
module { name = "ratbox" }

 :P

EDIT:
Why is not supported? :(
Logged

Adam

  • Team
  • *
  • Offline Offline
  • Posts: 463
Re: Anope disconnected (charybdis 3.3.0)
« Reply #3 on: June 01, 2012, 02:36:55 AM »

We don't support using protocol modules on IRCds they aren't designed for.
Logged

Mr. X

  • Anope User
  • Offline Offline
  • Posts: 3
Re: Anope disconnected (charybdis 3.3.0)
« Reply #4 on: June 01, 2012, 02:38:10 AM »

but why charybdis is not supported

(wow, this support site is very quickly :) )
Logged

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
Re: Anope disconnected (charybdis 3.3.0)
« Reply #5 on: June 01, 2012, 08:10:34 AM »

A decision was taken early in 1.9 to only support the most popular IRCds in the early development stages to avoid increasing the workload in maintaining protocol modules through each design change.

I would expect Charybdis support will come along when things settle down in 1.9 because it is a decent and well used IRCd.

:)
Logged
Pages: [1]   Go Up