stunnel cannot write to /var/run/stunnel.pid because it drops perms to nobody:nogroup when it starts. If I create the file /var/run/stunnel.pid and give nobody full (750) perms to it, stunnel will still not start because it needs to create the file itself. Reproducible: Always Steps to Reproduce: 1. emerge stunnel 2. /etc/init.d/stunnel start; /etc/init.d/stunnel stop 3. check stunnel.log, no stunnel running! Maybe this is an upstream issue, mainly because stunnel should not bail out if the pidfile is already available, but my current recommendation is to give stunnel its own user and give that user write access to /etc/stunnel, placing the pidfile in there.
i see that 4.04-r2 adds the stunnel user, but there are still no perms set on /etc/stunnel or the pid file
-r3 in CVS which should fix this and other stuff.
-r3 works great for me - thanks for the cleanup :)
*** Bug 37986 has been marked as a duplicate of this bug. ***
*** Bug 61077 has been marked as a duplicate of this bug. ***
