| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | BinkleyXE BBS Handoff |
... BJ> error level exit. This is NOT recommended under BJ> OS/2 (or Win32), and probably not recommended in BJ> Linux. If I remember correctly, the one I use is BJ> the SpawnBBS method, where Binkley starts up the BJ> Max process directly, passing commandline info, BJ> including (under OS/2) the needed handle to the BJ> serial port. [Under DOS, this passes the fossil BJ> port number.] I don't remember the third type at BJ> the moment. WG> WG> Any idea why errorlevel-exit isn WG> t recommended? It doesn't seem like such a horrible way WG> to do things, although I would personally prefer WG> spawning the BBS directly from the mailer (assuming the WG> mailer doesn't try and diddle the com port into the WG> controlling tty or something equally annoying). Now that I understand how you are planning the intial modem implementation under linux, we probably can directly use the error level exit as one methoid under Linux. In OS/2, Binkley is passing a handle to the open port, which doesn't work if you close the program (exit) and let another program start. Under Win32, when you drop back to the shell (with the program exiting), it causes DTR to drop -- which most BBS sysops use to drop carrier and hang up the modem connection..... Since we aren't hitting either of those with your linux version, I stand corrected that the error level exit script processing should work..... If the DTR issue shows up in Linux, we can always submit code changes to fix that problem..... (and fix it on our own systems.) WG> How does Bink XE handle the errorlevel exit from Maximus? I have a "jury WG> rigged" solution in testing right now to "handle" WG> errorlevel exits from the forked maximus child (after WG> accepting a TCP/IP call) which actually re-calls the WG> runbbs.sh shell script and passes it its errorlevel on WG> the command line before dying. This allows me to use a WG> single script to control the ip inbound calls and the WG> serial inbound calls -- and have the serial calls WG> handled as traditionally as possible. Ok.... We should be able to use both the spawnbbs and error level exit options in binkley.... But this is just based on my assumption of how things should be working, based on how things work with DOS and OS/2..... Take care..... Bob Jones --- Maximus/2 3.01* Origin: Top Hat 2 BBS (1:343/41) SEEN-BY: 633/267 270 @PATH: 343/41 10/345 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™.