Differences

This shows you the differences between two versions of the page.

--- howto:systemd [2020/11/24 02:04] – Remove the setcap stuff (performed at build time now) digital man
+++ howto:systemd [2022/06/27 14:03] – [Ubuntu 16.04+] typo nelgin
@@ Line 1: / Line 1: @@
-====== Start Synchronet BBS from Systemd ======
+====== Start Synchronet BBS from systemd ======
-If you run a modern GNU/Linux distribution, you will likely discover [[https://en.wikipedia.org/wiki/Systemd|Systemd]] is used as the init system (for starting and control system services/daemons).
+If you run a modern GNU/Linux distribution, you will likely discover [[https://en.wikipedia.org/wiki/Systemd|systemd]] is used as the init system (for starting and control system services/daemons).
 In this case, instead of use the old SysV-style /etc/init.d/sbbs.service init script, you use a systemd services unit file:
 Create and edit (or download from [[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/install/systemd/sbbs.service|here]]) the following file (please correct your ExecStart path and User/Group as you need):
+===== Where is My Service File? =====
+If you are already running Synchronet from systemd but can't remember where the config file is, the following commands will help.
+''systemctl status'', then when viewing the file type ''/sbbs''. Note the service name (probably sbbs.service). ''q'' to quit back to the command line.
+Use that service name to return the path to the config file. Example: ''systemctl show -p FragmentPath sbbs.service''
 ===== Ubuntu 16.04+ =====
@@ Line 18: / Line 27: @@
   Type=forking
   Environment=SBBSROOT=/sbbs SBBSCTRL=/sbbs/ctrl
+  # this stops you running out of files
+  LimitNOFILE=10000
+  # this enables you to take a good core dump
+  LimitCORE=infinity
   User=sbbs
   Group=sbbs
@@ Line 67: / Line 80: @@
   Dec 11 20:24:03 HISPAMSX sbbs[1226]: term Node 1 thread terminated (0 node threads remain, 71 clients served)
+**NOTE**:\\
+If you're running any kind of recent (last 2yrs+) systemd, to avoid the use of ''[[howto:linux_non-root|setcap]]'' to run 'sbbs' as a non-root user, just put this line in the ''[Service]'' section of your ''sbbs.service'' file:  ''**AmbientCapabilities=CAP_NET_BIND_SERVICE**''
 ===== Monitoring with Byobu (Tmux backend) =====
 You can have a text mode dashboard for monitoring and configuring your BBS realtime by using Byobu with Tmux or GNU Screen backends. If you are using the Tmux backend. The following configuration splits your screen in three panes: one for SBBS log, other for UMONITOR and a last one for SCFG. Please note that this configuration assumes SBBSCTRL variable is set and that access permissions to the needed files are set for the current user.
@@ Line 119: / Line 134: @@
-Finally, you must execute //systemd daemon-reload// for tell systemd te reload the unit file
+Finally, you must execute //systemd daemon-reload// for tell systemd to reload the unit file
 Test your setup:
@@ Line 169: / Line 184: @@
 ===== Recommended Tweaks to the Service Section ===
-Add these to the ''[Service]'' section:
+Add these to the ''[Service]'' section of your service's config file:
 To increase the open file limit:
-  LimitNOFILE=10000
+<file sbbs.service>
+LimitNOFILE=10000
+</file>
 To allow core file generation (for crash/segfault debugging:
-  LimitCORE=infinity
+<file sbbs.service>
+LimitCORE=infinity
+</file>
 ===== See Also =====

howto/systemd.txt · Last modified: 2022/11/30 22:00 by digital man

Back to top