Quoting Peter Pentchev <roam@ringlet.net>: <snip>
You did not answer this question. However, I just realized something after reading Jochen Bern's reply: did you set `foreground = yes` in your config file? (as the last part of the per-config-file service section says you have to do)
Sorry, about not answering the question. It was the same output as what my previous e-mail had. That aside, adding foreground=yes in the myconffile.conf fixed the issue. I did read that in the README.Debian, but stupidly dismissed that because I wasn't intending to create a per config-file setup. However, I think that file needs updating, and my assumption is that it isn't part of the original package. I'd like to make a PR or some suggestions for changes, what is the best way to go about that? For anyone following, the final solution for me to get systemd and disable the initd on Ubuntu was to do the following: in my config file for stunnel, make these changes: foreground=yes setuid = stunnel4 setgid = stunnel4 pid = /var/run/stunnel4/stunnel4.pid in /etc/default/stunnel4, change ENABLED=1 to ENABLED=0 so that the initd won't start at boot. Maybe we can provide a sample conf to work for Debian/Ubuntu and make good default choices? Mike