I don't know if my case is related to yours, because I don't have the necessary skills to inspect the init.d script, but I cannot start stunnel4 with "sudo /etc/init.d/stunnel4 start", so neither stunnel starts when i boot my workstation.
Instead "sudo stunnel4" works perfectly. Best regards -- stunnel4 init.d script reports startup failures with pid=error message even when not so https://bugs.launchpad.net/bugs/137472 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
