It looks like the relevant portion of the stunnel log is: 2014.03.06 06:40:52 LOG6[18041:3073944384]: Local mode child started (PID=18055) 2014.03.06 06:40:52 LOG7[18041:3073944384]: Remote FD=1 initialized 2014.03.06 06:40:52 LOG3[18041:3073944384]: TCP_NODELAY: Socket operation on non-socket (88) 2014.03.06 06:40:52 LOG5[18041:3073944384]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
Does this mean something to someone? It's as though stunnel is trying to set a socket option on stdout or something... any help with this would be appreciated, I'm surely not the only person with this issue. Thanks, Ron On 03/05/2014 08:28 AM, Ron Aaron wrote: > Actually, it's really an stunnel question. > > I am experimenting with using stunnel on my server for fossil access (I > currently use Apache+SSL). > > If the stunnel is configured to run in "foreground", everything is fine; > but if not, it fails with a "read error". I assume this is a technical > problem I can fix in the stunnel.conf, but so far I haven't had success. > > Any suggestions? > > Thanks, > Ron > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
