touched in the first place (Twice the bugs in half the time!) use
use -D_THREAD_SAFE to compile object files for a threaded app (You have to
do that on BSD already anyways)

Removed excessive #ifdef __QNX__ blocks.

Eliminated some comment-out code.

Checking return value of getnodedat() before calling putnodedat().

mod.

here.

Renamed "curr_socket" local var in input_thread to just "sock".

realloc it.

Linux		    No		    Yes
FreeBSD		    Yes		    Yes
OpenBSD		    No		    No
NetBSD		  Yes(lib)	    No
QNX		    No		    Yes

*sigh*

Get rid of startup.h kludge but makeing YIELD() an empty macro in nopen and
getuserdat

*blush*

Of course, Win32 could use a real yield *hint hint*

NOTES:
------
startup.h has an ugly YIELD kludge in it, and includes both ringbuf.h and
threadwrap.h.  However, it is sometimes used in non-threaded utils.
This must be fixed!

if the child changes ANY value.

command from any JS-enabled system/service (not just the BBS).

background process wiyld take down the whole BBS.

program... kludged, not fixed.

wrapper... so just use fcntl() locks.  Also, if it is flat out impossible
for anyone to ever get a lock on a particular file (ie: is a socket) do not
fail.

Note: This trick may come in hady for a future locking solution.

this:

Whever a user connects to a node, the unix domain socket localspy.sock is
create in the node directory.  This is a RAW connection to the users data
stream.  This is NOT a telnet connection.  Do NOT telnet to the UDS... you
will not like the results.  However, you can easily and safely do something
like:

cat /sbbs/node1/localspy.sock

Possibly netcat will allow you to remote control a users session... not
sure if nc supports unix domain sockets or not.   Have fun with this one.

to create a file as now are 0700

brokenest under QNX.