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 Message-ID: <435F56CB.4EBEB22C@dessent.net> Date: Wed, 26 Oct 2005 03:13:31 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Running ssh in background [solution/patch] References: Content-Type: text/plain; charset=iso-8859-1 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 j9QADeRT029732 Jörg Schaible wrote: > OK. Works in rxvt, but not in a plain Windows console. That's because rxvt doesn't use a Windows console, it uses a Cygwin pty. -mwindows essentially just tells the system to not allocate a Windows console to the process when it is created. This means if the program reads or writes its I/O through a pipe or file redirection it will be fine, but if it is expected to output to or from a console it will fail because nothing is connected. The process can manually allocate a console for itself, but that's extra needless complication. (And from what I recall of the setup.exe --help threads, there's also some complication with an API that only exists on XP and beyond.) > > 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. You might make more traction by suitably patching the 'run' utility so that it also supports pipes. Then you could use 'run' to launch the standard /bin/ssh without the console window. Brian -- 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/