Current stunnel-init-script did not use start-stop-daemon. if stunnel crashes it is not possible to detect this with /etc/init.d/stunnel status. (We need this to monitor stunnel via corosync) Also using symlinks (stunnel.config1 -> stunnel) seems to be a more sophisticated approach ... Reproducible: Always
Created attachment 283737 [details] stunnel.initd
I agree that this is a much simpler and elegant approach. I just pushed the init script on stunnel-4.44-r1. Thanks for submitting!