TIP: Click on subject to list as thread! ANSI
echo: muffin
to: Bob Jones
from: Bo Simonsen
date: 2003-10-10 10:23:40
subject: Long `unzip` time

Hello Bob!

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

 BS>> (A danish pop band did actually made a song there is
 BS>> named Dr. Jones, are you a Ph.D? ;))

 BJ> No, or not yet.....

Are you studying?

 BJ>> Based on how the telnet code is currently working (for as far as
 BJ>> Wes has progressed the code to date), the WFC screen is needed.

 BS>> Unfortionally it's.. Made because Wes, do only emulate
 BS>> the modem, by implementing the write/get calls to the
 BS>> modem.

 BJ> Basically true.  But it is done that way because that is how Max is
 BJ> coded for hooking into right now.....

Okay, I didn't look so mutch in the WFC source, so I know how things works..

Actually I did more concentrate on Squish..

 BJ>> The
 BJ>> telnet code is only a single line support right now, and is like
 BJ>> running a barefoot maximus or opus under DOS or
 BJ>> OS/2 (or Windows).  To
 BJ>> get to the point of multi-line, the telnet stuff will need to be
 BJ>> changed.

 BS>> Automatically it's multiline. (It's here..)

 BJ> And how are you handling multiple telnet sessions at one time?

 BJ> (a)  Are you Starting each up on a different tcp/ip port?

No on the same.. It can just take more users.

 BJ> (b)  Are you running a copy of Maximus for each telnet session?

No.. It starts automatically with the runbbs.sh script?

 BJ>> To prove that you only have a single line BBS support, try
 BJ>> to make 2 or more telnet sessions to the same maximus telnet port
 BJ>> at one time.  Only the first will succeed.....  And if you bring
 BJ>> up a second copy of max/Linux for handling a second telnet port,
 BJ>> you will have to use a different TCP/IP port number.

 BS>> Well yes it handles only one telnet port, but more than
 BS>> one can be logging into the system at one time!

 BJ> How are you starting maximus for this?  I don't think I've seen that
 BJ> work.  How are the BBS sysop consoles handled in this siutation?

I'm using the script which is included in the contrib dir afair.. Here is it:

=== Cut ===
#! /bin/sh
#
# $Id: runbbs.sh,v 1.3 2003/07/05 00:13:51 wesgarland Exp $
#
# $Log: runbbs.sh,v $
# Revision 1.3  2003/07/05 00:13:51  wesgarland
# Fixed bugs processing echomail/netmail, etc
#
# Revision 1.1  2003/06/12 02:09:56  wesgarland
# Initial Revision
#
#
# {at}file         runbbs.sh
# {at}author       Wes Garland
# {at}date         May 25 2003
# {at}description  A helpful script for running Maximus under
#               UNIX. Ideal for init:respawn monitoring.
#

PREFIX=/home/ftn

MAXIMUS="${PREFIX}/etc/max.prm"
PATH="${PATH}:/${PREFIX}/bin"
LD_LIBRARY_PATH="${PREFIX}/lib:/usr/local/lib:${LD_LIBRARY_PATH}"

minDynNode=3

export PREFIX PATH LD_LIBRARY_PATH minDynNode

rm "${PREFIX}/die.now"
cd ${PREFIX}

while /bin/true
do
  [ -f "${PREFIX}/die.now" ] && break
  bin/max -dl -w -b38400 -n0 -p2000
  sleep 1
done
=== Cut ===

 BS>> Well why don't write a natively TCP/IP connection module?

 BJ> This is where the maxpipe and other issues may come in.  I believe the
 BJ> (current) design of maximus includes a sysop console per available
 BJ> connection....

Hmm.. Afaik is the sysop login just starting up like another maximus process?

Or is the sysop console the WFC screen?

 BS>> [IPC]

 BJ> All user interactions are displayed on their screen and on the sysop
 BJ> console for that session.  So, the basic IO package is configured for
 BJ> this.....

 BJ> What was your question?

Can't remember now..

 BS>> Why actually using VMODEM? Why not native TELNET?

 BJ> Because maximus (under DOS, Win32 and OS/2) does not support native
 BJ> telnet.

But it could (easyly?) be ported, for win32.. I'm not scure about OS/2..

Well Wes is modulizing the communication module, so on DOS you only
compiles the "POTS" module..

 BJ> It support only what it thinks is a modem for the user.  Max
 BJ> was designed to control a modem off a serial port interface, with a
 BJ> sysop console on the system console....

Hmm..

 BJ> To do anything else is a
 BJ> major code change....  Which is also why Wes did the telnet support
 BJ> the way he did (for now)......

Yes..

Regards,
Bo

--- GoldED+/LNX 1.1.4.7
* Origin: The Night Express, Roennede Dk (2:236/100)
SEEN-BY: 633/267 270
@PATH: 236/100 237/9 20/11 106/1 2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.