Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20001205162626.020e8110@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Tue, 05 Dec 2000 16:31:19 -0500 To: craig DOT hayes AT lmco DOT com, cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: RE: Bug: Cygwin crashes when bash is called repeatedly from a .ba t file Cc: ed DOT maksimowicz AT lmco DOT com In-Reply-To: <31A81CDD9175D411815100508BE32AA62BCB44@emss02m13.ems.lmco. com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 04:14 PM 12/5/2000, craig DOT hayes AT lmco DOT com wrote: >I found the solution to this problem buried in a very useful Web page written by Steve Chamberlain (sac AT cygnus DOT com). The URL for the Web page is: > http://www.cl.cam.ac.uk/m3doc/linux/text/cygwin/faq.txt > >The pertinent parts of the Web page follow: >... >Installation >============ >... > For bash, you'll need to create a directory called `/tmp', and put a >copy of `bash.exe' into `/bin/sh.exe' and `/usr/bin/sh.exe'. >... >Bash says that it can't fork (or just hangs) - why ? >==================================================== > > Most often this is because it can't find itself in the path. Make >sure that your path includes the directory where bash lives, before you >start it. > > If you get errors like 'no such file or directory' when you're trying >to run a shell script, which you know is there, then your problem >probably that bash can't find `/bin/sh'. >... > > >Here is my question: If this is a known issue, why doesn't the installation GUI go ahead and do the copies for the user? That would have saved me a lot of grief, and I am sure that other people must encounter the same problem. > >Thanks, > > Craig Setup mounts /bin to /usr/bin and /usr/bin is where sh lives. At installation time, sh is NOT bash but ash. The only way you could run into the problem described by Steve now is if you modify your sh to be bash but do so inconsistently. That's my best guess as to why you had the problem. The issue Steve's note describes is not a problem with the current installer. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com