Okay, one more question about dpsm. I have removed the c2s section in
jabber.xml and replaced it with:
<service id='dpsm'>
<accept>
<ip/>
<port>5225</port>
<secret>dp5m</secret>
</accept>
</service>
I then try and run dpsm, but get the error:
Starting up...
configure()...
init()...
Could not create connection to jabberd
<?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' id='3B02E9D4'
xmlns='jabber:component:accept' to='dpsm'>
Ok.. so dpsm can't connect to jabberd apparently. I dig a little and
find that jabberd is listening on port 5222, not 5225:
tcp 0 0 *:5269 *:* LISTEN 4282/jabberd
tcp 0 0 *:5222 *:* LISTEN 4282/jabberd
I assume jabberd should be listening on port 5225 and dpsm on 5222,
correct? Anyway, I played with mio.c and found that mio_listen() is
using port 5222 regardless of the <port/> tag. This happens even with
the original c2s service:
<service id="c2s">
<load>
<pthsock_client>./pthsock/pthsock_client.so</pthsock_client>
</load>
<pthcsock xmlns='jabber:config:pth-csock'>
<authtime/>
<karma>
<heartbeat>2</heartbeat>
<init>64</init>
<max>64</max>
<inc>6</inc>
<dec>0</dec>
<penalty>0</penalty>
<restore>64</restore>
</karma>
<ip port="5999"/>
<!--
The <ssl/> tag acts just like the <ip/> tag. Except SSL is used
on the ports and ips specified. You must specify an IP here, or
the
connections will fail.
<ssl port='5223'>127.0.0.1</ip>
<ssl port='5224'>192.168.1.100</ip>
-->
</pthcsock>
</service>
Notice I am using port 5999, but jabberd continues to listen on ports
5269 and 5222 (instead of 5999).
Am I doing something wrong?
Regards, Dustin
--
Dustin Puryear <[EMAIL PROTECTED]>
http://members.telocity.com/~dpuryear
In the beginning the Universe was created.
This has been widely regarded as a bad move. - Douglas Adams
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
