Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 30 Jun 2003 20:27:06 +0100 (BST) From: andrew brian clegg X-X-Sender: fcleg01 AT sark DOT cryst DOT bbk DOT ac DOT uk To: cygwin AT cygwin DOT com Subject: Re: About the 'su' command In-Reply-To: <20030629233457.GY22695@ganymede> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact CCSG (http://www.cryst.bbk.ac.uk/CCSG/) more information X-MailScanner-cryst-bbk: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-31.6, required 9, BAYES_01, EMAIL_ATTRIBUTION, FROM_ENDS_IN_NUMS, IN_REP_TO, QUOTED_EMAIL_TEXT, QUOTE_TWICE_1, REPLY_WITH_QUOTES, USER_AGENT_PINE) On Mon, 30 Jun 2003, Karsten M. Self wrote: > on Wed, Jun 18, 2003 at 08:51:24AM -0400, Bill C. Riemers wrote: > > Now you ask, "Well then, why can ssh do pipes." Very simple, 'ssh' sticks > > around after starting the child process starts passing data from open file > > descriptors though sockets. Bit of a tangent, but -- did anyone ever figure out what all those transient connections between non-priv ports on localhost are for when you type stuff into an ssh session? There was a bit of discussion on here a few months ago about it, but I'm not sure it ever got resolved, and I've just started to see it myself having finally installed ssh... Andrew. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/