X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Problem when using variable assignment, backticks in shell script Date: Wed, 30 Aug 2006 15:50:19 -0400 Message-ID: <017630AA6DF2DF4EBC1DD4454F8EE29708DCEA55@rsana-ex-hq1.NA.RSA.NET> From: "Silva, Russell" To: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k7UJoVoX022362 Hi Dave, I've tried to reproduce the problem on a different computer without success. So, the problem appears to be specific to this particular machine. Are there any characteristics of my machine that could influence bash's ability to fork/exec processes? How can I further diagnose this problem? Thanks to all of you that informed me about alternatives to cat; unfortunately, the problem crops up with other programs (wc is the one I'm actually using), so avoiding cat doesn't solve my problem. In any case, it's pretty weird that bash randomly fails to spawn child processes! It wreaks havoc on a number of my scripts. Regards, Russell RE: Problem when using variable assignment, backticks in shell script * From: "Dave Korn" * To: * Date: Tue, 29 Aug 2006 22:51:58 +0100 * Subject: RE: Problem when using variable assignment, backticks in shell script On 29 August 2006 22:00, Silva, Russell wrote: > Hi Dave, > > I tried this; it's an excellent point but isn't the problem. I > experimented using your script version and $? is indeed set to 0 when > the backtick output is empty. > > I'd be happy to hear more suggestions. I also need to try this on > another machine (my home box, perhaps) to see if it's reproducible on > other machines. Have you tried any of these scripts to see if it's a > problem general to Cygwin users? Yep, I tried >> before I thought about modifying it. Didn't get the error to occur. Will run it a few more times and see. Am using self-built version of cygwin1.dll from 20060720. I'll see what happens with a more recent version as well. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/