Subj : BinkD
To   : Bob Jones
From : Russell Tiedt
Date : Fri Oct 10 2003 11:09 pm

Hello Bob.

08 Oct 03 13:36, you wrote to me:

<-->

 RT>> Yeah, setting it to run on a different port appears to
 RT>> be simply a matter of
 RT>> setting iport and oport, I presume as follows,

 RT>> iport binkp 24555
 RT>> oport binkp 24556

 BJ> I believe the port number is supposed to be the only option after the
 BJ> iport or oport key word.  If the port number is a name (such as
 BJ> binkp), then I believe the code is looking it up in the standard table
 BJ> (/etc/services on most linux or unix systems.  Under OS/2, I believe
 BJ> the services file is burried where some of the other TCP/IP
 BJ> configuration files are located.)  So, if I am correct, you really
 BJ> want:

 BJ> iport 24555
 BJ> oport 24556

Hmmm ... from other posts, and the docs, what I have had time to read, tend 
to support that. :-))

 RT>> But my problem is that BinkP on MBSE is run from
 RT>> inetd.conf, and it appears
 RT>> that if there is a binkp line in inetd.conf then BinkD
 RT>> will not run in daemon
 RT>> mode on my Binkley system, which is how I want to run it. :-((

 BJ> If you were using your stated lines ('iport binkp 24555' and 'oport
 BJ> binkp 24556') then I think Binkd was still trying to use the standard
 BJ> ports (binkp), and ignoring the 24555 and 24556 port numbers.

Okay.

Thanks,

Russell

--- GoldED+/LNX 1.1.4.7
 * Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)

.