Subj : Re: Getting the telnet port number
To : Ree
From : Digital Man
Date : Thu Jan 27 2011 02:23 pm
Re: Re: Getting the telnet port number
By: Ree to Digital Man on Wed Jan 26 2011 07:38 pm
> > That's wierd, server.socket should definitely be defined. What version
> > of Synchronet are you using?
>
> The latest developer build EXEs for Windows, which are dated May 2010.
> Here's the results of a for (var prop in server) log(LOG_DEBUG, prop + "="
> + server[prop]);
>
> 1/26 10:24:43p 0632 WebSocket JavaScript service thread started
> 1/26 10:24:43p 0632 WebSocket version=Synchronet Services 1.245
> 1/26 10:24:43p 0632 WebSocket version_detail=Synchronet Services 1.245
> Compiled May 14 2010 05:07:32 with MSC 1200
> 1/26 10:24:43p 0632 WebSocket interface_ip_address=0.0.0.0
> 1/26 10:24:43p 0632 WebSocket options=2048
> 1/26 10:24:43p 0632 WebSocket clients=1
>
> which does match what I found in the documentation here:
>
http://www.synchro.net/docs/jsobjs.html#server
Okay, server.socket is only defined for *static* services (e.g. ircd.js), so
that checks out. The original question was how to discover the *Telnet* port,
and server.socket.local_port would only do that if the script was running in
the context of the Telnet server, so I think the point is moot and the sbbs.ini
parsing is probably your best bet. I would use the file_cfgname() method to get
the correct sbbs.ini filename derivation however, as there can be multiple
sbbs*.ini files to choose from.
digital man
Snapple "Real Fact" #81:
Alaska has more caribou then people.
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net
