for the static 64-byte sbbs->telnet_cmd buffer, it will bork the session.
(Seen with a long user-name and DISPLAY when using the OS X telnet client).

the login process a bit (e.g. using Unix 'telnet -a <host>').
Treat login name provided via RLogin, SSH, or Telnet equally (e.g. use in new
user signup by default).
Disable the hard-coded bypassing of netmail address prompts for RLogin
users (there are other ways to accomplish this, e.g. using JS if desired).

- this option has been a default option flag for 10 years
- this option was introduced *before* the RLogin password capability
- Synchronet now always expects the login-ID (alias) to be the 2nd string
received during RLogin connections (called 'server-user-name' in RFC 1282.
* Now storing the complete terminal type/speed string received during RLogin
connection in the bbs.rlogin_terminal property (sbbs_t.rlogin_term in C++).
* bbs.rlogin_gate() is over-hauled:
- arguments are: address, client-user-name, server-user-name, terminal, mode
- if existing JS module assumes this to be: address, server-user-name, password
  those scripts will need to be updated to reflect the correct argument order
- all arguments beyond the first are now optional
- the terminal string can now be passed-in
* Deprecated the telnet gateway option: TG_SENDPASS (the 'password' if desired
to be sent as the 'client-user-name' can be specified as an argument and this
option sent the password as the *second* RLogin string ('server-user-name'),
which was always wrong.
* sbbs_t::telnet() can now accept the terminal string as an optional argument.

timed events, QWK call-out nodes, etc.) when the server has been terminated.

related crashes (mainly due to null pointer dereferences of scfg_t members
freed in cleanup()).
Use of new protected_int_value()  for extra paranoia (but can't use it on
destroyed protected-int's).

Deuce.

constructors and destructors?

Prevents telnet options from getting set incorrectly.

realloced variables for tracking QWKnet nodes discovered while importing msgs,
but multiple terminal server nodes/events calling this function concurrently
could clearly corrupt these variables and cause realloc errors and crashes.
Now using members of sbbs_t for node/event instance specific QWKnet
node tracking for the route.dat updates (a rarely used feature nowadays).

This should really get a new file with happy wrappers at some point - I'm not
sure where lprintf() will go if it happens from main() right now etc.

ssh session.

Improved Telnet option processing and event execution log output.

files are not created as root.

seconds, just continue waiting (and logging warnings).

was false (which is the initialized value). This is an expected case for the
terminal server. Added note to self (or others) not to do that. :-)

output_thread is terminated (for some uknown reason, perhaps due to the
new checking of the "online" value): outbuf will never drain if the
output_thread isn't running, and possibly, even if it is (but there is no
connection).
Added error logging during node status change in dailly_main().

and leave it rooted until the script is done or the context is destroyed.

This should clean up crashes before a script starts (ie: While creating
common objects)

has its own functional "too much recursion" detection.
Replaced "branch callback" stuff with "operational callback".
JavaScriptBranchLimit has been replaced with JavaScriptTimeLimit
(default value: 24 hours)

functions when an excpetion is pending.

Some work still needs to be done on js_msgbase.c,  js_user.c, and mailsrvr.c

all exported functions and data types using a 32-bit time_t (time32_t).
(part 2 of 2)

(node_threads_running) wasn't being re-initialized upon recycle, so the node
would lock/crash attempting to lock an uninitialized mutex upon answering an
incoming connection.