Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Tue, 5 Nov 2002 12:56:37 -0800 (PST)
From: "Peter A. Castro" <doctor AT fruitbat DOT org>
To: ljubomir DOT milanovic AT philips DOT com
cc: cygwin AT cygwin DOT com
Subject: Re: cygwin - novell interaction
In-Reply-To: <OF701203EC.84003C10-ONC1256C68.0066613E@diamond.philips.com>
Message-ID: <Pine.LNX.4.21.0211051241250.30332-100000@gremlin.fruitbat.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 5 Nov 2002 ljubomir DOT milanovic AT philips DOT com wrote:

> Hi,
> 
> I can not reproduce the problem using the DOS batch script.

Does this only happen with Novell mounted shares, or with other network
mounts?  As an experiment, have another Windows machine share some
directory (with some file in it), mount it locally and run your the shell
script against it (Trying to isolate the symptoms).

You might check the Novell console log for error messages.  For that
matter, check the Windows Event Log on your machine for messages.  As a
last resort, running strace on grep might yield some information.
Something like this:

#!/bin/sh
cnt=0
while [ $cnt != 50 ]
do
 echo $cnt
 t=`strace -o c:/temp/grep.trc.$cnt grep someString /n/path/to/file`
 cnt=`expr $cnt + 1`
done

> For the batch script:
> ---------------------------
> Rem run forever
> :lab1
> find "someString" n:\path\to\file
> goto lab1
> ---------------------------
> everything is fine (of course, maybe is M$ just too slow
> to reproduce the problem ;)
> 
> When I start a similar shell script:
> -------------------------
> #!/bin/sh
> while true
> do
>       t=`grep someString /n/path/to/file`
>       echo  /n/path/to/file
> done
> -------------------------
> I receive soon a message from grep: "No such host or network path"
> and drive (server) is not accessible (also not for windows/dos). After
> some time (ca. 5 sec) the drive is again on-line (until the next crash).
> 
> Anyway, I did not realize any problems if I'm using native M$ tools or
> self made C/C++ programs (e.g. processing of large number of files).
> 
> Bye,
> Ljubo
> 
> 
> > This sounds more like a Novel Client issue than a Cygwin issue.
> > Try running the following DOS batch file (as, say, xxx.bat).  Note that
> > this does not use any Cygwin commands at all and will only test the file
> > access from a pure Windows/DOS environment:
> >
> > Rem run forever
> > :lab1
> > type n:\path\to\network\file
> > goto lab1
> >
> > Be warned, that on a fast machine, it's difficult to break out of the
> > batch loop.  But, if it errors out, then it's not Cygwin that's at fault.
> 
> 
> 
> --
> 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/
> 

-- 
Peter A. Castro <doctor AT fruitbat DOT org> or <Peter DOT Castro AT oracle DOT com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood


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