Home | Networks | Community | Need Help? 

 
 Quick search

 
 
 RegisterRegister   Log inLog in 

Bahamut 1.4.36 friendly services?

 
Post new topic   Reply to topic    SearchIRC Forum Index -> IRCD & Network Services
Author Message
Guest






PostPosted: Apr 29, 2004 11:58am    Post subject: Bahamut 1.4.36 friendly services? Reply with quote

anyone know of any dalnet style services avaliable for bahamut 1.4.36?
ive tried all of the ones i can find but none of them support this version. i get the error :
17:12] -irc.gridlockfm.co.uk- *** Global -- from services.gridlockfm.co.uk: PANIC! buffer = :irc.gridlockfm.co.uk SJOIN 1083262318 #jo + :@skandal
-
[17:12] -irc.gridlockfm.co.uk- *** Global -- from services.gridlockfm.co.uk: Live Long and Prosper - Time to go Hold me please! I dont want to leave! buaaa!
-
[17:12] -irc.gridlockfm.co.uk- *** Routing -- from irc.gridlockfm.co.uk: Received SQUIT services.gridlockfm.co.uk from services.gridlockfm.co.uk[unknown@0.0.0.0] (Services terminating: Segmentation fault)
-
[17:12] -irc.gridlockfm.co.uk- *** Notice -- services.gridlockfm.co.uk was connected for 31 seconds. 0/2 sendK/recvK.
Back to top
uchat
Idler
Idler


Joined: 17 Mar 2004
Posts: 335

PostPosted: Apr 29, 2004 4:12pm    Post subject: Reply with quote

Nearly all GPL IRC Services that have NickServ/Chanserv/MemoServ support Bahamut.

http://www.anope.org
http://www.ircservices.za.net
http://www.habber.net/services

just to name a few.

But your error looks more like a configuration error than incompatability.

Make sure you have the right IRCd Type specified/compiled
Back to top
Guest






PostPosted: Apr 30, 2004 12:51am    Post subject: Reply with quote

ok well ive sorted half the error.. i changed the ircd i was using to an older version and services now seem to stay.
Now the problem is they dont 'do' anything, i can register a nick but after setting the enforce and set kill on it doesnt give them 60 seconds to change, after a channel is registered nothing happens, no +rtn or akicks or +o by chanserv.. rootserv 'access denied' even when i identify to the services master nick.. im using bahamut 1.4.33 and sirv2.9.0 - ive tried other services and they are the same... any ideas what im doing wrong here? services are 'there' and responding, but just being a bit lazy really..
Back to top
uchat
Idler
Idler


Joined: 17 Mar 2004
Posts: 335

PostPosted: Apr 30, 2004 3:53am    Post subject: Reply with quote

make sure you have a U:Line for Services

IF your serious about running an IRC network, you should choose a set of Services that are being developed (sirv is not, at least last I heard) or find yourself a coder to keep up with todays ever changing IRC technology. I personally recommend Anope http://www.anope.org
Back to top
Guest






PostPosted: Apr 30, 2004 5:27am    Post subject: Reply with quote

yes theres a U:Line for services..
i was using sirv as it has rootserv, what other services offer rootserv aswell as operserv ns cs etc etc
Back to top
Horizon
Lurker
Lurker


Joined: 10 May 2003
Posts: 145
Location: Regina, Saskatchewan, Canada

PostPosted: Apr 30, 2004 7:15am    Post subject: Reply with quote

uchat wrote:
Nearly all GPL IRC Services that have NickServ/Chanserv/MemoServ support Bahamut.

http://www.anope.org
http://www.ircservices.za.net
http://www.habber.net/services

just to name a few.

But your error looks more like a configuration error than incompatability.

Make sure you have the right IRCd Type specified/compiled


Actually IRCServices does not support the newest bahamut. See http://www.ircservices.za.net/version5.html
Back to top
uchat
Idler
Idler


Joined: 17 Mar 2004
Posts: 335

PostPosted: Apr 30, 2004 2:46pm    Post subject: Reply with quote

Quote:

yes theres a U:Line for services..
i was using sirv as it has rootserv, what other services offer rootserv aswell as operserv ns cs etc etc


Most have either RS or OS, very few have both. In fact I really don't see a need for both, however Cygnus does, it's found at http://www.habber.net/services but Cygnus is slow to update and is nearly a dead project as well.

If I may .. why would you need both OS and RS?
Back to top
Ashen
Idler
Idler


Joined: 05 Jan 2004
Posts: 285

PostPosted: May 01, 2004 8:36am    Post subject: Reply with quote

Anonymous wrote:
ok well ive sorted half the error.. i changed the ircd i was using to an older version and services now seem to stay.
Now the problem is they dont 'do' anything, i can register a nick but after setting the enforce and set kill on it doesnt give them 60 seconds to change, after a channel is registered nothing happens, no +rtn or akicks or +o by chanserv.. rootserv 'access denied' even when i identify to the services master nick.. im using bahamut 1.4.33 and sirv2.9.0 - ive tried other services and they are the same... any ideas what im doing wrong here? services are 'there' and responding, but just being a bit lazy really..

make sure you're oper'ed up too.
Back to top
rakaur
none
none


Joined: 09 Feb 2004
Posts: 10

PostPosted: May 02, 2004 6:11pm    Post subject: Reply with quote

.36 completely bastardized the protocol by trying to add sid+uid systems. It didn't turn out too pretty. I don't know how well the backwards compatibility works.
Back to top
Monosex
none
none


Joined: 08 Apr 2004
Posts: 14

PostPosted: May 04, 2004 7:30am    Post subject: Reply with quote

rakaur wrote:
.36 completely bastardized the protocol by trying to add sid+uid systems. It didn't turn out too pretty. I don't know how well the backwards compatibility works.


Well i'm using 1.4.36 with ircservices 5.0.31 and have no problems at all. I know that it works with anope, too.

edit:
bahamut 1.4.36 doesn't have sid+uid, it's a part of 1.6 branch (no longer developed) and is in TODO for future versions of 1.8, which will be released in a week or so.


m.
Back to top
Display posts from previous:   
Post new topic   Reply to topic    SearchIRC Forum Index -> IRCD & Network Services All times are GMT - 6 Hours
Page 1 of 1

 
 
Forum powered by phpBB
 
 © 2000 - 2008 EverythingIRC, Inc. All rights reserved. Please read our disclaimer