With the caveat that I do not use fastcgi myself, this sounds like reasonable default behaviour so a reuse_socket option might not be necessary at all.
Laurence On 29 November 2010 15:00, Grzegorz Nosek <r...@localdomain.pl> wrote: > Hi, > > The attached patchset allows multiple fcgi-programs to share sockets. After > applying, a new boolean option 'reuse_socket' is available (default: false, > for compatibility). Enabling this option and specifying the same socket= for > multiple process groups makes fd 0 of all processes from these groups point > to the exact same socket. > > Without this option the behaviour is somewhat unexpected (I'd say buggy): > Unix sockets are created sequentially so all but the last one to bind to a > specific path will _never_ get a connection (their fd 0 is unreachable from > the file system) and duplicate TCP sockets make supervisord explode at > startup (an unhandled exception and crash, leaving the first process running > and forever occupying the socket). > > The patchset is lightly tested and appears to work fine. > > BTW: supervisord's option handling is very unclear for me (a twisted maze of > almost dict-like classes, all alike), so buyer beware. > > Best regards, > Grzegorz Nosek > > _______________________________________________ > Supervisor-users mailing list > Supervisor-users@lists.supervisord.org > http://lists.supervisord.org/mailman/listinfo/supervisor-users > > _______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org http://lists.supervisord.org/mailman/listinfo/supervisor-users
