| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,T_RP_MATCHES_RCVD |
| X-Spam-Check-By: | sourceware.org |
| Message-ID: | <5016A62C.3070600@cs.utoronto.ca> |
| Date: | Mon, 30 Jul 2012 11:20:12 -0400 |
| From: | Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca> |
| User-Agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 |
| MIME-Version: | 1.0 |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: sshd crashing |
| References: | <CA+7conmf=HORJ9nscNe4CA67EAeO+n7H6GkpVK4cPq315wJtzg AT mail DOT gmail DOT com> <CAHiT=DFFxBH=EoQx1karYBhAEVmNk1n9Ocn6kjLvnjWboXJ7Ow AT mail DOT gmail DOT com> <CA+7con=1XYjoJ1ZK2tRcF5jQG5KEcmkup2ZOO+0MazfeyeT=5g AT mail DOT gmail DOT com> <20120728021859 DOT GA13502 AT ednor DOT casa DOT cgf DOT cx> |
| In-Reply-To: | <20120728021859.GA13502@ednor.casa.cgf.cx> |
| X-IsSubscribed: | yes |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
On 27/07/2012 10:18 PM, Christopher Faylor wrote: > On Sat, Jul 28, 2012 at 01:04:47AM +0200, Pawel Jasinski wrote: >> as I said I did rebaseall :-( >> In a mean time I also tried with CYGWIN=pipe_byte, no change >> At the moment of crash there is nothing new in the /var/log/sshd.log > Oh boy. "CYGWIN=pipe_byte" will now become the voodoo fix for the masses. > I should have seen that one coming. > > For the record, there is absolutely no reason to use pipe_byte with Cygwin > programs. FAQ entry? It might work to have documentation for each CYGWIN= value that says specifically what it will *not* do. For example, pipe_byte will *not do anything* for cygwin programs, ttysec will *not do anything* at all, etc. Added bonus: a link for google to point the masses at that's *not* a third-party cygwin support page filled with out of date voodoo. Ryan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |