Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Mon, 10 Mar 2003 08:39:33 -0500 (EST)
Message-Id: <200303101339.h2ADdXEC015644@skunk.nvs.com>
From: "Richard H. Broberg" <rhb AT inficon DOT com>
To: maxb AT ukf DOT net
CC: cygwin AT cygwin DOT com, Richard DOT Broberg AT mail DOT inficon DOT com
In-reply-to: <057301c2e510$7a8c7ce0$78d96f83@pomello> (maxb@ukf.net)
Subject: Re: cygwin/1.3.20-1 bash child process disassociation behavior weirdness
References: <200303072147 DOT h27Llr8Q012503 AT skunk DOT nvs DOT com> <038a01c2e4f4$fbd8fc90$78d96f83 AT pomello> <200303072238 DOT h27Mctko020526 AT skunk DOT nvs DOT com> <057301c2e510$7a8c7ce0$78d96f83 AT pomello>

>  Resent-To: Richard DOT Broberg AT mail DOT inficon DOT com
>  Resent-From: rhb AT inficon DOT com
>  From: "Max Bowsher" <maxb AT ukf DOT net>
>  Date: Sat, 8 Mar 2003 01:17:25 -0000
[snip]
>  
>  Richard H. Broberg wrote:
>  >>  From: "Max Bowsher" <maxb AT ukf DOT net>
>  >>
>  >>  An unfortunate consequence of how Windows handles console windows.
>  >>
>  >>  I believe it would be possible to write an alternative
>  >>  implementation of nohup using fork/setsid, or perhaps even hack
>  >>  some changes into the Cygwin DLL.
>  >>  But it's now just a configuration issue - it will take some coding.
>  >>
>  >
>  > hmm...I feared as much.  Can you give me details on 'of how Windows
>  > handles console windows'?
>  
>  Not specifically. I have a pretty good idea where I'd go looking to find
>  out, but I don't have the information at my fingertips.
>  
>  (I'd look at the MSDN AllocConsole/FreeConsole docs, and follow links from
>  there)
>  
>  > Surely it's not
>  > impossible; the windows' command 'start' basically 'does the right
>  > thing', and the semantics of 'start' are basically no different than
>  > 'nohup command &'.
>  
>  I've a feeling start will still open a console window.
>  
>  > When you say 'console windows' do you mean
>  > 'console linked app', as in the /SUBSYSTEM:CONSOLE silliness in
>  > win32 link-land?
>  
>  No, I mean the window Windows provides to run such apps in.
>  

hmm, and yet after seeing responses to this list that rxvt works
(which I verified for myself), I am compelled to believe that this
isn't the whole story.  The fact that rxvt works (without special
builtin hackery) makes me think that bash should be able to as well.
If the problem is truly the windows 'window' behavior (which I'm
not convinced it is either, see my 'look how the windows "start"
command works in a window), then why not have bash be in a window
more like rxvt instead of more like cmd.exe?

These are only suggestions at this point, of course, until I roll
up my sleeves to address the problem for real.  In the meantime I'll
happily use rxvt in place of bash, since it does what I need.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/