https://gitlab.synchro.net/main/sbbs/-/commit/1581ed4b45b9f6d6ef7c63d7
Modified Files:
src/sbbs3/ftpsrvr.c mailsrvr.c main.cpp services.c websrvr.c
Log Message:
Use protected_int*_adjust[_fetch]() correctly

At least on Linux/GCC, std-atomic version of xpdev/protected_int API was only used when building .cpp files and the _adjust() functions returned a different value from the .c files since they used the mutex versions of these functions/ macros. Use the _adjust_fetch() versions of the API when the return value is used (and assumed to be the *new* / adjusted value of the integer).

It's possible for other tool-chains or target platforms, the .c usage was
wrong as well (assuming the *new* integer value was returned rather than the old), if they built with std-atomic support for C.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/1ec7cb53a8f52df12d6623e7
Modified Files:
src/sbbs3/ftpsrvr.c mailsrvr.c main.cpp services.c trash.c trash.h websrvr.c
Log Message:
Support a filter (*.can) file 'quiet' attribute (e.g. "q=1")

A dubious feature. This will squelch any "CLIENT BLOCKED" type log messages assocated with a filtered client. Importantly, other log messages related to the client connection won't be (can't be) squelched, so this isn't going to really be a useful feature in my opinion, but when sysops ask for this (e.g. silently-blocking specific hostnames), I want to be able to demonstrate why that's not really practical.

The syntax is "<filter-string><tab>q=1" if you want to play with it.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net