[JDEV] Newbie: Who should be using the jabber software ?
tcharron at ductape.net
Wed Nov 24 09:48:29 CST 1999
Quoting "John P. Looney" <jplooney-jabber at online.ie>:
> > > then. Maybe it's trying to connect elsewhere...
> > Your command line was using a secret of 'bing'?
> hey...it's only a test box :)
No, I was more questioning that you where starting jserver with a different
secret then was in the registry you pasted.. ;-P
> > The above line lists the transport as a dso transport, which is *TADA*
> > most likely automatically loading into memory FOR you. Try to telnet
> > 5222. If you get a connection, jserver is already loaded. That's the
> > of the dso usage. It loads it using shared memory instead of connecting
> via a
> > socket.
> That is so cool. But, er...it wasn't documented :) Or at least I couldn't
> see it.
We're working on the documentation for everything as we speak..
> Right. So I've got etherxd running, and seemingly starting up jserver.so
> It's printing:
> SERVER CLOSED CONNECTION! (Err: 1)
> on startup though. Etherxd isn't printing much of interest. Can i get
> jserver to printout more useful debugging stuff, seeing as it's being
> loaded as a shared library, not as a program ?
Hrm. Jer? temas? I'm not sure why it would print a server closed
connection message using shared memory. Two things you can try:
A) Remove the dso attribute. This will prevent it from being loaded in
shared memory. Basically, when etherxd sees a transport line with a dso
attribute, it loads it from a library and uses shared memory. You can then
start up jserver as you where trying to do, using a socket connection. then
you can jserver -D -s secret and see more output
B) Look at the logs. The location of the logs is inside of the transport
entry in the registry. By default, it's
/usr/local/var/log/jabber/etherxd.error, etherxd.log, and jserver.log.
<< Wanted: One decent sig >>
<< Preferably litle used >>
<< and stored in garage. ?>>
More information about the JDev