... from the other Synchronet servers and services.

For advanced uses/debugging.

sd_notify() is called from other threads (PIDs), so we've been getting
syslog warnings abouts this and I hadn't noticed:

systemd[1]: sbbs.service: Got notification message from PID 2555007, but reception only permitted for main PID which is currently not known

As pointed out by Accession (PHARCYDE) on DOVE-Net.

Some shell pwd implementations default to the "Logical" PWD, which
can contain symlinks.  The POSIX standard for /bin/pwd is to return
the "Physical" PWD with all symlinks resolved.  Some shells don't
support the -P option the the built-in pwd, so we don't want to
reply on that.

For some reason, we're redefining the PWD env variable which should
by the phyical path, but I'm not really interested in tracking down
all the windy history for this.

Basically, this bit me once, and now it's fixed.

Apparently the cwd is changed back after ever command is invoked.

<nelgin> git -C /home/bbs/sbbs/repo remote set-url origin https://gitlab.synchro.net/main/sbbs.git
<nelgin> Unknown option: -C
<nelgin> using GNUMakefile on CentOS 7

This partially reverts commit 34909899

I'm using this on cvs.synchro.net along with an override.conf file in
/etc/systemd/system/ircd.service.d/

[Service]
ExecStart=
ExecStart=/sbbs/exec/jsexec -A -L7 -hcvs.synchro.net ircd.js -a cvs.synchro.net
LimitCORE=infinity

Add some handy tips too (querying status, monitoring log output)

'chown' resets Linux capabilities (e.g. cap_net_bind_service=ep), so these
calls reset the earlier bind-capabilities enablement, meaning the auto-setup
feature on Linux-install really never worked?

I think this addresses issue #403, at least in part.

We have no sbbs man page (that I know of).
The SBBSROOT env var isn't used anywhere.
NotifyAccess is required for the (new to v3.20) systemd integration support
We can just use the AmbientCapbilities to set the bind capability now
Set the open file limit to something huge (10000 files should be enough)
Update the instructions/comments.

This reverts commit cc53c94a.

SETCAP isn't a command-line after all, it's a build target.

This reverts commit 269968d7.

SETCAP isn't a command-line afterall, it's a build target.

So use 'whereis' to find and and 'cut' to trim its output

<Dan_C> DigitalMan: minor install issue noted today - during a fresh (Linux) install on a test box, the build failed because it was unable to execute the "sudo setcap ..." command.  This was on Slackware 15.0, where the setcap executable is located in /sbin , and that directory is not in the $PATH of a normal user, or even when a normal user uses the 'sudo' command.

Also include SETCAP in the set of documented make variables.

ecWeb is only web UI included/installed
Optional to enable 16-bit DOS support on 64-bit Windows now (since we support NTVDMx64 now).
Add libarchive.dll and zlib1.dll
Always install old 16-bit DOS utils (e.g. svdmansi.com), just in case

As reported via irc by Nelgin, the setcap target was not being passed
to 'make -C src/sbbs3' by default (on Linux) due to a misplaced paren.

Fixes issue #252.

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).

This can be used to defeat the automatic inclusion of the sbbs3
"setcap" build target when building on Linux. This should address
issue #175.

This resolves the issue of node2+/node.cnf file missing.

Needed to pass path to the "src" (SRC_ROOT), not SBBS_SRC.

Also updated the gitlab URLs to use main/sbbs instead of sbbs/sbbs.

Just in case the sysop chose not to specify SYMLINK=1.
As reported by Dan_C via IRC, thanks.

The webv4 directory is now part of the repo, so install it to the
install target directory too.

When SYMLINK=1 is used, symlink the following directories (rather
than copying): docs, exec, text, web, webv4, and xtrn. This will
hopefully make subsequenit updating (via git) easier for most sysops that use
this installation method. Let the merge conflicts insue.

Left it there, but commented out, just in case anyone needs it later.
But it was reported that the setcap line failed anyway:
Sep 24 09:20:15 bbs setcap[21466]: Failed to set capabilities on file
`/sbbs/repo/src/sbbs3/gcc.linux.*.exe.*/sbbs' (No such file or directory)
Sep 24 09:20:15 bbs setcap[21466]: The value of the capability argument is not
permitted for a file. Or the file is not a regular (non-symlink) file

Run-time dirs are ctrl, text, docs, exec, xtrn, web, node1