Subj : Re: 21:1/10 HUB
To   : Avon
From : Zip
Date : Sat Dec 10 2022 09:53 am

Hello Avon!

On 10 Dec 2022, Avon said the following...
 Av> Looks like BinkD had crashed for approx 7+ hours, I have restarted
 Av> things and packets are flowing again. Thanks :)

Glad to hear it's up and running again! :)

If the binkd process exited and you're running the binkd service using systemd, you might wish to add a local override for its configuration by running 'systemctl edit binkd' and pasting the following into the empty area at the top:

[Unit]
StartLimitIntervalSec=0

[Service]
Restart=always
RestartSec=30

....and saving and exiting the editor.

This will place your additions into an override file,
/etc/systemd/system/binkd.service.d/override.conf.

The additions will ensure that systemd will try to restart binkd forever every 30 seconds until it succeeds if it ever exits on its own (i.e. without 'systemctl stop binkd').

The systemctl edit command will automatically make binkd pick up
the new configuration (if you place such an override file manually on disk, you would have to run 'systemctl daemon-reload' manually for it to pick up the new configuration).

Then you just restart binkd with 'systemctl restart binkd', and you should be all set. Also try 'systemctl cat binkd' and see that it will show your overrides somewhere in there.

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

.