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 Message-ID: <3DB8777C.5050104@upb.de> Date: Fri, 25 Oct 2002 00:43:08 +0200 From: =?ISO-8859-1?Q?Sven_K=F6hler?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: de, en MIME-Version: 1.0 To: John Vincent CC: gp@familiehaase.de, cygwin@cygwin.com Subject: Re: Cygwin Here power toy References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Oct 2002 22:43:09.0093 (UTC) FILETIME=[B9C3AD50:01C27BAE] > The "exec" before the second invocation of /bin/bash means that > this replaces the first bash, rather than having the first bash > wait for it to finish. Thus, you should not end up with two copies > of bash in memory. (This depends, of course, on the correct > implementation of the exec() functions in the cygwin1.dll) > > /John Vincent. Than this is a cygwin-bug? (now i remember what exec means, isn't there an exec() in perl, too?) i definitly get 2 bash.exe in the NT-taskmanager, and the first bash.exe keeps holding a handle to it's current dir. -- 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/