Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
howto:systemd [2016/11/21 10:24] – add tmux screenshot ragnarok | howto:systemd [2019/09/04 13:22] – typo digital man | ||
---|---|---|---|
Line 5: | Line 5: | ||
Instead of use the old / | Instead of use the old / | ||
- | Create and edit the follow files (please correct your ExecStart path and User/Group as you need): | + | Create and edit the follow files (please correct your ExecStart path and User/Group as you need): |
+ | |||
+ | ===== Ubuntu 16.04+ ===== | ||
+ | / | ||
+ | [Unit] | ||
+ | Description=Synchronet BBS service | ||
+ | Documentation=man: | ||
+ | After=syslog.target network.target | ||
+ | |||
+ | [Service] | ||
+ | Type=forking | ||
+ | Environment=SBBSROOT=/ | ||
+ | User=sbbs | ||
+ | Group=sbbs | ||
+ | PermissionsStartOnly=true | ||
+ | ExecStartPre=/ | ||
+ | ExecStart=/ | ||
+ | ExecReload=/ | ||
+ | Restart=on-failure | ||
+ | RestartSec=30 | ||
+ | |||
+ | [Install] | ||
+ | WantedBy=multi-user.target | ||
+ | |||
+ | Some points in this config: | ||
+ | * **After**. If you are using syslog with sbbs, so it is nice to put that requirement before systemd tries to launch sbbs. | ||
+ | * **Type**. If you are to run SBBS in daemonized mode, the main executable will exit after the daemon is called. This could confuse systemd into thinking the process is finished. If you use " | ||
+ | * **Environment**. In order to avoid having multiple files, you can embed the variables inside the service file. | ||
+ | * **User/ | ||
+ | * **PermissionsStartOnly**. This one tells systemd to execute ExecStartPre as root, but ExecStart as the user and group declared in User, | ||
+ | * **ExecStartPre**. Capabilities are lost from the sbbs executable every time it is recompiled. It is possible to mitigate the effect by running setcap just before the daemon is ran. The binding won't fail anymore using this. Please notice you can't point a symlink here, so modify the architecture directory to the right path (gcc.linux.x64.exe.release or gcc.linux.exe.release). | ||
+ | * **ExecStart**. If you don't want to get syslog entries duplicated you will have to run SBBS in daemonized mode, so the " | ||
+ | * **RestartSec**. It's advisable to wait some secs before attempting restarting in case of failure, just to give some time for binding release. | ||
+ | |||
+ | Installation instructions: | ||
+ | -Modify the environment variables to match your SBBS setup | ||
+ | -Modify User and Group. If you run this as root you don't need the ExecStartPre line. | ||
+ | -Modify the ExecStart and ExecStartPre paths to match your Synchronet setup. | ||
+ | -Place this file in the correct location. For Ubuntu 16.04 you should place it in / | ||
+ | -Enable the service with " | ||
+ | -To run the service without restarting " | ||
+ | |||
+ | Running //systemctl status sbbs// will show: | ||
+ | |||
+ | ● sbbs.service - Synchronet BBS service | ||
+ | Loaded: loaded (/ | ||
+ | Active: active (running) since Thu 2016-12-15 20:20:43 CET; 16s ago | ||
+ | Docs: man:sbbs | ||
+ | | ||
+ | | ||
+ | Main PID: 12374 (sbbs) | ||
+ | | ||
+ | Memory: 30.1M | ||
+ | CPU: 223ms | ||
+ | CGroup: / | ||
+ | └─12374 / | ||
+ | |||
+ | Dec 15 20:23:25 HISPAMSX sbbs[1226]: term Node 1 Telnet | ||
+ | Dec 15 20:23:31 HISPAMSX sbbs[1226]: term Node 1 Terminal not detected, reducing inactivity hang-up timeout to 75 seconds | ||
+ | Dec 15 20:23:36 HISPAMSX sbbs[1226]: term Node 1 Unknown User ' | ||
+ | Dec 15 20:24:02 HISPAMSX sbbs[1226]: term Node 1 disconnected | ||
+ | Dec 11 20:24:03 HISPAMSX sbbs[1226]: term Node 1 thread terminated (0 node threads remain, 71 clients served) | ||
+ | |||
+ | ===== 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. | ||
+ | |||
+ | Create the file '' | ||
+ | |||
+ | new-session sbbs ; | ||
+ | new-window -n sbbs tail -n 50 -f / | ||
+ | split-window -h / | ||
+ | split-window -t 1 -v / | ||
+ | set-option mouse on | ||
+ | |||
+ | And then run: '' | ||
+ | |||
+ | If you want this to be your default environment when you log at your Synchronet server, then write the configuration to the '' | ||
+ | |||
+ | The following screenshot shows the result: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | If are using also **binkd** for FidoNet, this configuration will split the dashboard in 4 panes: | ||
+ | |||
+ | new-session sbbs ; | ||
+ | new-window -n sbbs tail -n 50 -f / | ||
+ | split-window -p 50 -h / | ||
+ | split-window -t 0 -p 20 -v tail -f / | ||
+ | split-window -t 1 -v / | ||
+ | set-option mouse on | ||
+ | |||
+ | {{: | ||
+ | ===== Debian & CentOS 7 ===== | ||
- | ===== Debian ===== | ||
/ | / | ||
SBBSCTRL=/ | SBBSCTRL=/ | ||
Line 77: | Line 168: | ||
{{: | {{: | ||
+ | |||
+ | ===== Recommended Tweaks to the Service Section === | ||
+ | Add these to the '' | ||
+ | |||
+ | To increase the open file limit: | ||
+ | LimitNOFILE=10000 | ||
+ | |||
+ | To allow core file generation (for crash/ | ||
+ | LimitCORE=infinity | ||
===== See Also ===== | ===== See Also ===== | ||
* [[: | * [[: | ||
- | + | * [[https:// | |
- | {{tag>}} | + | {{tag>linux systemd}} |