&time is incremented after maint runs, which allows a newly created
first user to take turns on the first new day.

When viewing messages posted with pipe codes (e.g. coming from Renegade, WWIV,
Mystic BBS), the wordwrap logic would prematurely wrap lines.

This is highly unlikely to solve whatever is happening on DMs system

Since this script isn't normally calling bbs.nodesync() (e.g. to display
any pending inter-node messages/telegrams), we have to check the NODE_INTR
flag manually. Calling bbs.nodesync() directly here to get a more immediate
notice and disconnection message sent to the user.

This check is necessary so that a sysop or the event thread can gracefully
terminate/disconnect a user that's running this script (e.g. when an
exclusive timed event is scheduled to run and thus being prevented to run).
This should help Keyop's reported issue with his weekly msgmaint timed event
having to ungracefully disconnect his user session because he's running this
script.

and abort the execution of the program when the node is interrupted. This
should allow more cases were the node interrupt flag can be used to gracefully
disconnect a user running a DOS or native (stdio) program on *nix.

We have this functionality already in the Windows version of external()

When a timed event is configured to run "exclusively", all nodes need to not be
in in-use. As it was, after waiting 60 minutes for the online user(s) to
notice they'd run out of time and disconnect, we'd just (rather ungracefully)
close the sockets used by such node(s) connections. This results in same logged
errors about trying to send to bad socket descriptors and provides no feedback
to the user about why they were disconnected.

Since we have the node interrupt flag (which hopefully, all scripts are
checking via node_sync) - use that to try to more gracefully terminate the
user's session/connection after 30 minutes of waiting for the user to
disconnect.

If after 60 minutes of waiting, the node is still in-use, we still do the
socket disconnection method.

Just caught during code review

This would've prevented some JS log functions from writing to the node.log file
(which gets concatented onto the daily "system" log files).

This just came up via code review while looking into Keyop's reported error:
term Node 2 !ERROR 9 (Bad file descriptor) in main.cpp line 4606 (node_thread)
     truncating "logfile" access=0

This is likely unrelated since the "logfile" is immediately re-opened after
executing the external program/script.

Not sure this makes any difference, but this matches LORD2 behaviour.

Should make issue #392 go away, but the underlying CNW bug which
will cause the player that runs maint to see all NPCs remains.

For CNW, maintenance should absolutely be ran as a timed event,
with a real name that never gets an account.  Luckily, if there's
no dropfile, real name defaults to SYSOP, which should meet that
criteria.

Maybe something will end up being useful, nobody actaully seems to
notice it happening though.

Reported by Digitalman

Since this doesn't work, we're clearly not relying on it, so remove
it.

Reported by: jrtc27 via IRC

This returns bug-compatibility with attrstr(), at least for Ctrl-A chars,
so that if someone is for example, assigning a Ctrl-A sequence to JS
console.attributes, that'll work (again) as it did in SBBS v3.19.

Any other invalid chars in the string will stop the parsing, still, even
though that's not how attrstr() worked.

For Kirkman's doorgame/script backward compatibility.

For Wildcat (N)ewsletter command and PCBoard "NEWS" command, display
"No news is good news." instead. :-)

DD file & message area choosers: Name collapsing now supports an arbitrary number of levels

See merge request !520

... when using the -mail option, which probably no sysop is.

Just needed to set the 'can_read' property.

As reported via IRC by Accession

Log errors if/when comWriteBuf() fails.

This is to hopefully help to root-cause or even possibly resolve the issue
reported in #synchronet by PyRoDrAkE:
"It all works well until the Dialup connection runs slower than 4800 baud
using SexPots. I connect from my XT at either 1200 baud or 2400 baud and it
would just stop drawing midway."

There shouldn't be any write timeout in comWriteBuf(), so I don't know why
this would help, but it's worth a try. Logging any comWriteBuf() errors is
also a good idea in general.

and if the message is UTF-8, encode the origin line as UTF-8 too.
If the message is straight ASCII (e.g. the sub-board is configured as ASCII
only), convert the configured origin line to ASCII, before appending.

At this time, only ASCII and CP437 encodings of originlines are supported
in Synchronet (imported and exported origin lines can contain UTF-8).

This should address the issue raise by Sergey Dorofeev (2:5020/12000) in the
FidoNet UTF-8 echo whereby messages exported from Synchronet systems
(presumably using SBBSecho) could contain a mixture of CP437 and UTF-8
encodings (!) when the sysop had CP437 chars in their configured origin line.

I sent an update ("add" email), but it was rejected with
"No LSM entries were found" - whatever that means.

... so yeah, most *nix sysops will get a warning about running something newer
than the latest release.

... for a version number comparison (e.g. by chksetup.js)

This file hasn't been updated in 20 years and nobody noticed. :-)

I at least made a new submission (sent email) one last time before we
(might) just remove this file since the the LSM database doesn't appear
to be of any real use/value these days.

This fixes the bug whereby if the user ever hit Ctrl-C or hit 'N' at
a pause prompt, they could never see another menu / display file.

When displaying this node vstatus, the user's alias shouldn't be appended to
the node status, else you get something like this:

16  Logging out Digital ManDigital Man

It was possibly before for fgets() failures to be pretty hard to diagnose.

But set the error string to hopefully be printed as a warning

A sysop could hit 'q' to quit (sbbs, console mode) while the binding is taking
place.