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: <003201c36130$72ba6ad0$200aa8c0@thorin> From: "Carlo Florendo" To: Cc: "Menon, Girish \(MED, WIPRO-GE MED\)" References: Subject: Re: Backtick does not work Date: Wed, 13 Aug 2003 08:18:39 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 > That's not a bash script, that's an 'sh' script. Which is ash on > cygwin. Maybe ash doesn't support back-tick? If you change your > /bin/sh to /bin/bash it should work. Ash supports the backtick. The section of the script which Girish posted should work without problems in bash, sh, and ash. > > Menon, Girish (MED, WIPRO-GE MED) wrote: > > From the bash shell the ` (backtick or command execution) work. But when > > I spawn a process and execute a shell script which contains the back > > ticks, the process just chokes. > > > > For example, a simple shell script like > > #!/bin/sh > > .. > > .. > > myenv=`/bin/env | grep CYGWIN` > > .. > > .. > > > > I am able to execute this script properly from the bash shell (as any > > user on the system). I am not getting any error at all from the > > execution of the script. It just quits. I checked the error code too. It > > is 0. > > But this same script when executed via a spawned process does not work. -- 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/