From owner-freebsd-current Sun Jul 14 14: 8:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E735237B400 for ; Sun, 14 Jul 2002 14:08:10 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id BC75343E42 for ; Sun, 14 Jul 2002 14:08:09 -0700 (PDT) (envelope-from marc@informatik.uni-bremen.de) Received: (qmail 24354 invoked from network); 14 Jul 2002 21:06:33 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.82.121.246) by www.contentmedia.de with SMTP; 14 Jul 2002 21:06:33 -0000 Subject: mysterious dead-locks with system ssh From: Marc Recht To: current@FreeBSD.ORG Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 14 Jul 2002 23:08:07 +0200 Message-Id: <1026680887.757.9.camel@leeloo.intern.geht.de> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm getting strange dead-locks/complete lookups when I use the system ssh with port forwarding. Using something like: ssh -L8080:remote:8080 account@remote to forward a remote apache to my local box. When I access http://localhost:8080/ not later than the third click on link (or pressing reload) my box locks up completely. I don't even get into the debugger or get a crash dump. The box is just plain dead. Though "normal" SSH works perfectly and accessing a local (not forwarded) apache works, too. The world and kernel is of today and IIRC this actually did work last week (or the week before). Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message