I've resolved my issue simply setting "ENABLED=1" instead of "ENABLED=0" in the file /etc/default/stunnel4. Tatiana, I still don't know if your case is affected by the same issue, but my problem now seems quite stupid. To be honest, it seems also quite stupid that file didn't enable the service, and that I had to search in the instructions given by the library department of my university to solve the problem (BTW: FANTASTIC! Detailed instructions for Ubuntu 7.* and Gentoo).
-- 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
