Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Subject: RE: Running ssh in background [solution/patch]
Date: Wed, 26 Oct 2005 12:04:54 +0200
Message-ID: <F0D7281DAB048B438E8F5EC4ECEFBDDC506E11@esmail.elsag.de>
From: =?iso-8859-1?Q?J=F6rg_Schaible?= <Joerg DOT Schaible AT Elsag-Solutions DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j9QA59K3028672

Corinna Vinschen wrote on Wednesday, October 26, 2005 11:57 AM:

> On Oct 26 11:40, J?rg Schaible wrote:
>> My solution was to build ssh as Windows console app: [...]
>> +sshw$(EXEEXT): $(LIBCOMPAT) libssh.a $(SSHOBJS)
>> +       $(LD) -mwindows -o $@ $(SSHOBJS) $(LDFLAGS) -lssh
>> +-lopenbsd-compat $(LIBS) +
>> [...]
>> Two questions:
>> 
>> 1/ Corinna, could you provide this version with next OpenSSH
>> releases, too? Setting the appropriate property in the Subversion
>> config to this sshw.exe, makes the SVN Clients in the Windows worlds
>> happy. Neither Subclipse nor RapidSVN show these steadily popping up
>> console windows anymore, nor does the command line version of
>> Subversion behave differently.
> 
> Sorry, no.  It's nothing I'm willing to support.
> 
>> 2/ If linking a normal console app as Windows console app does not
>> behave differently, why is it not the default? What's the real
>> difference for Cygwin? It is still a Cygwin app and is normally
>> listed in the Cygwin processes. I cannot say too much about the pipe
>> and forking stuff, but something like "tar cf - *.sh | sshw spk1 tar
>> xf -" works just normal.
> 
> Just open a console window and call "ssh".  What you see is
> the help text.  Now try the same with "sshw".  What do you
> see?  The difference is that the sshw process doesn't connect
> to the console.  That's nothing I'd want in the Cygwin distro.

OK. Works in rxvt, but not in a plain Windows console.

> It seems easy enough to build ssh this way if that's what you need.

For personal need yes, for distribution in an organisation, this is different. Maybe more complaining users might change your mind some day ;-) At least it is in the records now.

- 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/