As Deon pointed out:

I saw that smbactive was removed recently (719b7523), but a quick search of
code, sees reminants in GNUmakefile and other files, which I'm wondering is a
cause of the problem...?

We've never really cared how many times the ring buffer has become
empty, how many times data was added to it, or how many times we've
been over the highwater mark.  These have effectively always been
event signalling, with extra hackiness to clear "extra" semaphore
posts.

This commit removes RINGBUF_SEM entirely, and uses events for
everything.  There's an empty event (set when the ring buffer is empty),
a data event (set when the ring buffer is not empty), and a highwater
event (set when the ring buffer has at least highwater mark bytes).

A RingBufWrite() will set data and highwater events if applicable,
and clear the empty event.

A RingBufRead() will set empty event and clear data and highwater
events if applicable.

RingBufReInit() will now set the empty event, and clear the data
and highwater events.

These are the only actions the RingBuf API will perform on the
events, it does *not* clear the highwater event on a RingBufWrite()
if the buffer does not have enough bytes in it for example, this
will *only* be done by RingBufRead() or RingBufReInit().  This
allows consumers to force specific behaviours (such as forcing
the highwater event on shutdown to prevent waiting for it).  Since
the current code was able to deal with the semaphores having
arbitrarily high counts, the existing code shouldn't have any
issue with this.

For things that want to shut something down, we're now setting both
the data and highwater events to ensure it doesn't wait for a
timeout (even for things that don't use highwater like the inbuf).
The RingBuffer API should grow a thing to do this (RingBufferFlush
perhaps?) rather than the consumers poking into the innards
arbitrarily.

Tested on the webserver and RLogin server and seems to be working
great.  sexyz builds.  It seems there's some Windows thing that
uses the ringbuffer sem for something, but I couldn't figure out
what... updated the build file, but no clue if that's broken or not
now... I'm sure DigitalMan will be happy to fix it if CI doesn't
catch it. ;)

This should allow the console object to grow a "flush" method that
will set the highwater and data events.

Kayz authored 4 years ago and Rob Swindell committed 4 years ago

The hardcoded external.bat file has been moved to a templated
/exec/external.bat which can be modified by the sysop. ENV
vars are in there to be able to customize as needed. emusetup.bat
is no longer needed, but still supported. The actual dosemu command line
is now stored in /exec/dosemulaunch.ini and can be customized for
fossil or i/o command lines. the keystroke is now only sent for i/o, and
only sent as \n instead of \r which would trigger undesired behavior in
certain programs. The above 2 files can also be placed in door dirs
to override. ansi.com has been removed as it was not needed. default
external.bat includes cmd lines for share, x00, etc. (user will still
need to provide these in xtrn/dosutils).

FidoNet NetMail can now be gated to an SMTP client (as before), but replies are
now successfully gated back to FTN NetMail. This uses a new more RFC-compliant
To/From address header field format, so older messages (previously gated to
an SMTP client) cannot be successfully replied-to. Tested with Microsoft
"Windows Live Mail 2012" (previously known as Outlook Express).
Test reports/results with other SMTP mail clients would be welcome.

Requires SBBSecho v2.30 or later. File attachments are not yet supported.

FidoNet netmail in the normal mail base (data/mail.*) will now be exported to
FTS-1 (*.msg) files automatically. One way in which the FTN netmail can end up
in the mail base is by using the (legacy/runemaster) Web UI. You should also
get the updated savemsg.ssjs if you're going to use this feature.
To disable this feature use the (new) '-c' option.
Normally, the exported msgs will be deleted unless the '-d' option is used in
which case the messages are just marked as "sent", so they won't be exported
again. This feature does not yet support file attachments.

This will likely lead to the SMTP server supporting the sending of FTN netmail.
Apparently we have to find a better way to encode FTN addresses within
RFC2822-compliant header fields first.

If you're using a BSO/FLO-style mailer, this feature works with the '-f' option
so the full path of an outbound netmail may be SMB->*.MSG->PKT. Direct
export to PKT is certainly possible in the future.

Incremented SBBSecho version to 2.30.

Add support for USE_DOSEMU and BUILD_JSDOCS

from everything that links with the sbbs library.

Also, use the absolute path to the 3rdp stuff to silence CMake warnings.

sbbs3 into the top-level list to avoid infinite recursion when a sub-projects
include the sbbs3 list for libsbbs.so.

Include uedit/umonitor.

CMake default is release.

switchover to CMake.

DLL linkage to sort out though.

only so far.  Next is making it work in Windows, then generic working on
all other *nix platforms.