This variation on fcntl() record-locks resolves multiple-thread / forking
issue with region locks. No longer falls back to using flock() (whole-file
locks), when OFD locks are available and used successfully. At the least,
this should provide a performance boost for shared files using region
locks (on Linux). No change for Windows (region locks already worked sanely
among multiple threads) and other *nixes (that use POSIX fcntl() locks
only).

(credits) to use the full 4 gibibyte range of a 32-bit unsigned integer:
max-out at 4,294,967,295 instead of 2,147,483,647.
Since these values are stored as 10 characters, we could theoretically extend
the range to 9,999,999,999 (credits/bytes) without changing the user.dat format
but is a bigger change (moving to 64-bit integers everywhere these values are
read or adjusted).

Only retain the last (most recent) 10 data/<id>.qwk.*.bad files and
data/file/<user-num>.rep.*.bad files.

(CID) variable, even when the client isn't SEXPOTS.

TERMINAL LOCATION NUMBER (RFC 946) in sbbs_t::telnet_location.

Some (older?) versions of fTelnet request to send this option to the BBS to
share the real IP address of the client. Accept this option (when using
"format 0") and store the first 32-bits (an IPv4 address) in the telnet
location storage / caller-ID information. The same place the telnet
SEND LOCATION value is stored if received.

Now, we're not requesting this option (e.g. with a Telnet "DO" command), but
fTelnet doesn't need that: It offers to send it, so we accept.

to put in the description (in strftime() format). Can also be used in
combination with '-t' if you want today's date/time instead.
It's not very clear from the help/usage output, but if you specify both -f
(or -F) and -t, you'll *only* get today's date in the description (not both
the file date and today's date).

"kludges ... should be ... terminated by either a carriage return, or the
(0xE3) QWK terminator" :-(

(not delete) from the end of the sorted list of files (normally, 0).
Created an sbbs_t::delfiles() wrapper which defaults to keep 0 files and also
generates a error.log message if any of the file-deletions fail.

(not delete) from the end of the sorted list of files (normally, 0).

deprecated

Elsewise if it's a number, treat it as a port.
The last "hostname" and "port" encountered on the commandline according
to these rules is what the websocket server done gonna connect to.

"Should" fix problem reported by Mortifis.

one.

Version 1.68: Each paragraph of text written in a message is now saved as one long line so that they can be wrapped appropriately according to the terminal/reader width (which should work online as well as in offline readers).  Also, message uploads are now supported by typing /UPLOAD (or /UL) on a line by itself (the uploaded message will replace any message written into the editor).  Also, now honors the SUB_ANON and SUB_AONLY flags for the sub-boards when cross-posting so that the "from" name is "Anonymous" if either of those flags enabled.

is being forwarded to an external email address. Introduced in rev 1.690,
user-forwarded emails wouldn't work because sending envelope would contain
the original forward-path. Thanks again to Alterego (ALTERANT) for testing
this stuff and reporting issues with detail!

(new). Reported by Alterego (ALTERANT)

A few *service.js scripts call this function without a password argument
(the second argument), e.g. login("guest");
If there was no guest account (or the guest account had a password assigned),
this would result in a failed login attempt as "guest" along with a garbage
password (e.g. a floating point number, like 3.7042561) and since it would
be a unique garbage password for each login() call without an actual password
specified, these login() calls would be counted as unique failed login attempts
and potentially cause the client's IP address to be added to the hack.log
and even ip.can (IP address filter).

As seen on Mortifis' system where VERT was filtereed due to
"SUSPECTED NNTP LOGIN HACK ATTEMPT", likely due to the daily sbbslist
verifications when just perform a TCP connection and no actual login attempt,
but nntpservice.js would still call login("guest") before the client (vert)
would be disconnected.

would reuse the same buffer where the message subject (list of filenames)
was stored causing havok. Reported by Alterego (ALTERANT).

P_OPENCLOSE mode flag is *not* specified, do not malloc()/read() the entire
file and then display. Instead, print one line at a time (so long as that
line is <= 1MB in length), calling putmsg() for each line.

This should allow the viewing of massive text files in SBBS again without
alloc/swap issues.

I left the calls to utf8_normalize_str() in here, but I'm not so sure about
them now. putmsg() will convert UTF-8 to CP437 through print_utf8_as_cp437(),
and that only lacks a couple of conversions that utf8_normalize_str() does
(e.g. ellipsis to "..."), so that might be a good candidate to remove in
the future.

I'm not sure why I still run this service though...

the cause of lines of search results scrolling off the screen before an
auto-pause [Hit a key] prompt, would be displayed. Reported by Alterego.

to the bottom of Alterego's reported issue with new mail message bodies not
being displayed.

already creates the dirs that were of concern (Transfser File Paths). May
want to DLL-export this and call from here later.

in novice menu mode. :-)

line-counters knows the sysop (*not* in expert menu mode) hasn't seen the
printed-result.

Fixed typo in other log msg.

can't use it as an argument to sprintf(str, ...)
Also, use getfname()... more.

js_socket.obj : error LNK2001: unresolved external symbol _in6addr_any