You are not logged in.
Just a heads-up for stunnel4 users. For some reason, stunnel couldn't start on two Arch boxes after a recent u/g. This upgrade covered the last 4 days (12-15 through 12/20/11). Startup attempts were returning a spew that included:
chroot: No such file or directory (2)
After trying a couple of dead ends, including manually creating /var/run/stunnel (this allowed the service to appear to start, but not to create a pid), I found that a reinstall of stunnel4 did the trick.
--cheers.
Last edited by purple12 (2011-12-21 04:35:44)
Offline
Thanks for heads-up. Confirmed that reinstalling stunnel solves the problem.
Arch linux
Offline
I have the same problem, but it seems that I need to reinstalll stunnel everytime I boot the machine.
Is it the same for you?
cheers
Offline
Offline
Thank you, Falconindy
I will wait for the new version with corrected bug
Cheers
Offline