Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: Backticks hang with dynamic antivirus scanning
Date:	Wed, 18 Aug 2004 14:13:06 +0200
Message-ID:	<0C7AD907113E984F9C2AF0B651D0D3DE1F883D@exmid04.africa.enterprise.root>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Mike Kenny - BCX - Infrastructure Services" <Mike DOT Kenny AT bcx DOT co DOT za>
To:	"geneSmith" <gene DOT smith AT sea DOT siemens DOT com>, <cygwin AT cygwin DOT com>
X-OriginalArrivalTime:	18 Aug 2004 12:13:06.0367 (UTC) FILETIME=[B7DF74F0:01C4851C]
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id i7ICD9qB025131

You could try replacing all of your `command` syntax with $(command).
AFAIK, this was introduced with ksh way way back. The back tick support
was kept for compatibility with older bourne shell scripts. But at that time
AT&T were recommending $() syntax, though they also recommended that
root should use /bin/sh not /bin/ksh, go figure.

Anyway the replacement should work for scripts that you are developing.
If you have a large number of existing scripts maybe something like
sed -e "s/`.*`/$(&)/g"
(this might require a lot of excapes to work, YMMV)

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com 
> [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of geneSmith
> Sent: Tuesday, August 17, 2004 10:48 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: Backticks hang with dynamic antivirus scanning
> 
> 
> Marco Moreno wrote, On 2/20/2004 11:46 PM:
> 
> > I recently upgraded cygwin to the latest version and now I'm having
> > Command's dynamic antivirus protection conflict with Cygwin 
> so that it
> > hangs whenever it encounters backticks in a shell script (e.g.
> > /etc/profile).  Configuring the antivirus to ignore c:\cygwin had no
> > effect.  If I disable dynamic virus protection, all is well.
> > 
> > Has anyone else encountered this?  Has anything changed in 
> how backticks
> > are handled that might cause it to conflict with antivirus software?
> > Just trying to get a handle on this to submit a bug report 
> to Command
> > Software.  (Though I'm not holding my breath that they'll offer a
> > solution other than to avoid cygwin.)
> > 
> > Thanks,
> > 
> > Marco Moreno
> > 
> > 
> 
> No one answered this back in Feb that I could tell. I am seeing a 
> possibly related or similar problem. I am trying to build a 
> large shall 
> script based project under cygwin called RTEMS. It has been reported 
> that anti-virus can somehow affect the build and cause almost random 
> errors. I can't disable my a.v. since it requires a secret p/w. Could 
> this really be the problem?
> 
> -- 
> Lit up like Levy's
> 
> 
> --
> 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/
> 
> 

--
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/

- Raw text -