Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Running ssh in background Date: Wed, 26 Oct 2005 10:09:16 +0200 Message-ID: From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j9Q89PrO015549 Alexander Gottwald wrote on Tuesday, October 25, 2005 6:26 PM: > On Tue, 25 Oct 2005, Jörg Schaible wrote: > >> Good guess. While I have no console window popping up anymore, the >> ssh process does now no longer terminate and the Windows app hangs >> until I kill the ssh process :( > > most likely run.exe does not support piping or piping data to > a non-console application does not work at all. > > Why do you need cygwin openssh? the subversion plugin does > ssh connections too. Maybe puttys plink is an alternative. > TortoiseSVN has a version which is compiled > without console. Because I work extensivly with Cygwin, have already the ssh-agent up and use different private keys to access various sites. I don't want to start another agent just because of putty and configuring Subversion to use 1 key only is not sufficient. - Jörg -- 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/