GitLab

This won't impact Synchronet as it has a separate signal handling
thread, but we still need to behave properly for processes that
don't.  I'm also saying that ENOMEM does not indicate a disconnection,
though it may be better to pretend it was disconnected...

Don't return an error if the node#/node.cnf file can't be opened for all uses of load_cfg() except from the terminal server. This fixes #214 for Tracker1

We were just trusting that the error strings would be shorter than 256 (usually), but since we're including paths and strerror() results, we really have no control over the length of the error strings. So enforce some healthy boundaries. This could explain the crashes that Divarin of Mutiny is seeing with SCFG on WinXP or maybe it was the truncsp(strerror()) stuff that was just removed as well. We'll see...

The goal of this commit is that: only modules that either are part-of sbbs.dll/libsbbs.so or need to link with/use that library, will #include "sbbs.h" and thus be dependent on its subsequent includes (e.g. cryptlib.h, jsapi.h). This should mean extdeps.mk can be trimmed way down.

I also removed CVS keyword/comments and trimmed up the boilerplate copyright notice in modified and added source/header files in this commit.

There is no functional change in behavior in this comment.

If jsexec is used for a CGI script and the SBBSCTRL env var was not
set, a warning would be printed (to stderr), even if the -c option
was used to specify the path to the ctrl dir.

get_ctrl_dir() now accepts a boolean argument to specify whether to
print a warning when the default value ("/sbbs/ctrl") is used.
Pass FALSE for jsexec, TRUE for other callers (currently).

not set (or blank), use the default ("/sbbs/ctrl") and print a warning to
stderr. This resolves a FAQ for sysops that struggle with setting the SBBSCTRL
env var, but do have sbbs install in /sbbs or a symlink from /sbbs to where
sbbs is actually installed.

Note: this function is different than the one previously defined in getctrl.c
but never used. If/when we ever really need to support PREFIX, then perhaps
we'll use that one (which copies a string to a buffer).

I've likely broken something though, so if you see weird behaviour with
extended ASCII, let me know please.

as a command-line option can be problematic with *nix shells.

by properly const-ifying the appropriate functions and variables.

Not yet tested on Win32

startup option - we will *always* use the local timezone. If the sysop wants to
use GMT/UTC, they should configure their operating system accordingly.

uploaded to include the list output.

No more temp files in data or data/temp.
ctrl_dir/../temp (e.g. sbbs/temp) is the new default temp dir.
Each server has its own separately configurable temp dir.
BBS events (e.g. QWK packet processing) now have their own exclusive-use
temp dir (e.g. sbbs/temp/event).
All server threads will attempt to create and verify the validity of their temp dir.
System temp dir is only the default global temp dir for Unix (i.e. /tmp), since
the Windows default temp dir (e.g. C:\DOCUME~1\Rob\LOCALS~1\Temp) is not
particularly friendly or attractive.

or longer, uses a passed 'buflen' parameter to determine the truncation point.

Using memset() inplace of non-standard strset().