The problem seems to be caused by services sending a QUIT message for all the pseudoclients upon disconnection. If services just squits without sending the quit messages, bahamut handles "Services is currently down" response correctly. I am not sure If the ircd should handle this case differently (quit messages from pseudoclients), just reporting my findings Regards, Charalampos Pournaris Charalampos Pournaris wrote:
Hello,
I am experiencing a problem with the lastest version of bahamut - 1.8(06) (also tried the git version with ssl support) - and IRCServices 5.1.17. When services are connected to the network, everything works as expected and I get a response for commands like "NS HELP" but If for some reason services quits the network (SQUIT, Crash) and I send a command to the services, I get no response, instead of the "Services is currently down. Please wait a few moments, and then try again." message which is expected. If I restart the IRC server with no services on network, the "services are missing" message shows up normally. It's not that the services crashes too often, but it is a good indication for users to know that services are down instead of no response.
Thanks and regards, Charalampos Pournaris