open https://gitlab.synchro.net/main/sbbs/-/issues/733

When shutting down the BBS, the services thread does not tell you that it has been terminated.

```
Mar 3 20:44:15 bbs synchronet: Services thread still running
Mar 3 20:44:25 bbs synchronet: Services thread still running
Mar 3 20:44:35 bbs synchronet: Services thread still running
$ ps -ef|grep sbbs
bbs 1728171 1 4 Mar02 ? 01:15:56 /sbbs/exec/sbbs s! d
bbs 1773863 1352988 0 20:44 pts/0 00:00:00 grep --color=auto sbbs
$
Mar 3 20:44:45 bbs synchronet: Services thread still running
Mar 3 20:44:55 bbs synchronet: Services thread still running
$ ps -ef|grep sbbs
bbs 1773874 1352988 0 20:45 pts/0 00:00:00 grep --color=auto sbbs
$
```
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/733#note_5037

I suspect, in your case, services isn't actually terminating gracefully but is instead being killed (by systemd?).

When I test here with a stock config, I see that the syslog does indeed include the expected log message (''#### Services thread terminated''):
```
Mar 03 20:06:14 penguin synchronet[6693]: srvc 0000 Services terminate
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0004 NNTP closing socket 0.0.0.0 port 119
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0005 NNTP closing socket :: port 119
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0006 MSP closing socket 0.0.0.0 port 18
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0007 MSP closing socket :: port 18
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0008 ActiveUser closing socket 0.0.0.0 port 11
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0009 ActiveUser closing socket :: port 11
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0010 ActiveUser-UDP closing socket 0.0.0.0 port 11
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0011 ActiveUser-UDP closing socket :: port 11
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0012 Finger closing socket 0.0.0.0 port 79
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0013 Finger closing socket :: port 79
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0014 Gopher closing socket 0.0.0.0 port 70
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0015 Gopher closing socket :: port 70
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0018 WS closing socket 0.0.0.0 port 1123
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0019 WS closing socket :: port 1123
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0020 WSS closing socket 0.0.0.0 port 11235
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0021 WSS closing socket :: port 11235
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0000 Waiting for 1 static services to terminate
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0000 IRC !JavaScript warning /sbbs/exec/ircd.js line 156: Terminated
Mar 03 20:06:15 penguin synchronet[6693]: srvc IRC static JavaScript service thread terminated (0 clients served)
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0016 IRC closing socket 0.0.0.0 port 6667
Mar 03 20:06:15 penguin synchronet[6693]: srvc 0017 IRC closing socket :: port 6667
Mar 03 20:06:16 penguin synchronet[6693]: srvc 0000 Done waiting for static services to terminate
Mar 03 20:06:16 penguin synchronet[6693]: srvc #### Services thread terminated (0 clients served)
```

Is it possible you have a static service that isn't terminating? Looking closely at the "srvc" log messages after a termination has been requested might provide some more insight into what's happening.

And try running "sbbs s!" manually instead of via systemd to see if you find something else out.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)