X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.1 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,TW_RX X-Spam-Check-By: sourceware.org Message-ID: <4E1C4990.4050809@bonhard.uklinux.net> Date: Tue, 12 Jul 2011 14:18:08 +0100 From: Fergus User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Cygwin ML CC: Fergus Subject: Re: Random fork failures Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com >> Right. But rxvt crash. > I have no such problems with rxvt. Only incidental to the matters you have raised, but for what it's worth: Not quite certain what you mean by "rxvt crash" but with 1.7 I have repeatedly experienced "rxvt hang" - the rxvt session proceeds perfectly well until Ctrl-D to exit, and then the rxvt terminal just stays there, needing Ctrl-Alt-Del Task Manager to close it. (This phenomenon is frequent but not guaranteed. I have no idea what activity or activities induces it. With 1.5 Legacy there is no such problem.) When rxvt is started without switches in 1.7 the default terminal ("echo $TERM") is xterm. If I start with the explicit switch rxvt -tn cygwin to set TERM to cygwin then the "hang" problem goes away and rxvt works just fine. I don't actually "know" whether this is the cure, or even of the problem is common or well understood; maybe "rxvt -tn rxvt" would be a better switch to use. (People recommend mintty for 1.7 and probably with very good reasons, but I still quite like rxvt.) Fergus -- 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