[JDEV] irc-jabber & killall -HUP

[Keith Minkler]

<snip/>
> 1 - killall -HUP jabberd does not always (ever :) do what I expect it to, for 
> example if I add a new service to the jabber.xml file and -HUP jabberd it 
> doesn't act on it, for example start to listen on a new port (if I told it 
> to). This can be a bit annoying if people are using the server and I have to 
> take it down :-)

hehe.. doesn't always?  It doesn't really do *anything* ... =]  currently in jabberd, there is no way to reload the config file.. this good stuff is being saved either for 1.3 or 1.5, I don't remember which offhand... but I promise it will be much much cooler than previous jabber server stuff... we are going to be doing alot of dynamic config, remote admin stuff, services with TTLs, and other cool stuff, so that an admin can change the config file remotely, and have his changes go into effect immediatly.... that being said, it doesn't work yet... I believe the only thing it does on a HUP right now, is read the new config, and load it into it's greymatter__ variable, but it has no way of notifiying each component that the config has changed yet.. 

> 2 - I got icq-transport-0.9.something to work using groupchat. I changed a 
> few lines in the source (similar to other transports) and it worked like a 
> charm, connected to the irc server, etc. However, the most attractive feature 
> is to register with the agent and have it tell you when your friends come on 
> IRC. This uses the subagent register.irc.domain thing, and I haven't been 
> able to configure that properly with jabberd. I ended up with 2 accept 
> statements in jabber.xml (on service irc.domain and one register.irc.domain) 
> and adding one agent (irc.domain) that had a subagent register.irc.domain, 
> and well things got all complicated from there!

Yes, you will need two service sections for the register junk to work... kindof sucks, but I did it that way -- with the register subagent, with the promise that presence redirects would fix it, and make it seamless.. currently, it's really annoying for a client to register with irc transport, and some clients don't even support sub-agents!  maybe one of these days I'll see if i can merge the register code into the main agent... 

> I would be perfectly happy to use that irc-transport if I could get 
> registration to work (ie I haven't figured out all the details needed to set 
> it up with jabberd). 

I haven't tried it yet, to be honest, but you *should* just need two service sections... say one is ip 12.34.56.78:9000 secret:irc-trans and the other 12.34.56.78:9001 secret:irc-trans, (normally, you could just use one port, and connect them both to, and use different secrets to distinguish the id's, but this way you can just use the secret variable twice, with different ports)  give the first an id of irc.foo.com, and the second an id of register.irc.foo.com, (make sure these are set in the irc_trans.xml file as well) ...

you will also have to make the ehandler_new lines into ehandler_new_ex lines.. there are two of them in external.c, one for the main agent, and one for the sub-agent... just change them both.

<snip/>

-Keith