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: <057301c2e510$7a8c7ce0$78d96f83@pomello> From: "Max Bowsher" To: "Richard H. Broberg" , References: <200303072147 DOT h27Llr8Q012503 AT skunk DOT nvs DOT com> <038a01c2e4f4$fbd8fc90$78d96f83 AT pomello> <200303072238 DOT h27Mctko020526 AT skunk DOT nvs DOT com> Subject: Re: cygwin/1.3.20-1 bash child process disassociation behavior weirdness Date: Sat, 8 Mar 2003 01:17:25 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Please keep replies on the list. Richard H. Broberg wrote: >> From: "Max Bowsher" >> >> 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. Max. -- 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/