Re: cygwin - novell interaction

Re: cygwin - novell interaction

[ljubomir.milanovic]

Hi,

I can not reproduce the problem using the DOS batch script.

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/

Re: cygwin - novell interaction

[Peter A. Castro]

On Tue, 5 Nov 2002 ljubomir.milanovic@philips.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@fruitbat.org> or <Peter.Castro@oracle.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/

Re: cygwin - novell interaction

[ljubomir.milanovic]

Hi,

Just few words as a conclusion for Novell/cygwin problem.

In the meantime I could reproduce problem with
cygwin-independent C program (compiled by MS Visual Studio).
The problem ocures if many processes open/close files
on novell network very rapidly (MS batch is probably too
slow to reproduce the problem).

So, the problem has nothing to do with the cygwin, and I will ask
for help on some Novell forum.

Thank you very much for support and sugestions,
Ljubo


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

Re: cygwin - novell interaction

[Peter A. Castro]

On Tue, 5 Nov 2002 ljubomir.milanovic@philips.com wrote:

> Hi,
> 
> I'm using cygwin 1.3.12-2 on a Win2000 connected to a Novell
> network.
> 
> My problem is that if I access a network files rapidly the network
> connection breaks down after few seconds (10-20) and remote
> server is not accessible (also not for windows tools). The problem
> is hard to reproduce (often is everything working fine).
> 
> Following script illustrates the problem:
> 
> #!/bin/sh
> while true
> do
>       t=`grep foo /cygdrive/n/path/to/network/file`
> done
> 
> The problem persists also for 'n:/path...' filename form. If I add
> a 'sleep 1' command inside the loop or execute script on local
> drive everything is ok.

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.

> Thanx for any help,
> and sorry if the question is off-topic,
> Ljubo

-- 
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.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/

cygwin - novell interaction

[ljubomir.milanovic]

Hi,

I'm using cygwin 1.3.12-2 on a Win2000 connected to a Novell
network.

My problem is that if I access a network files rapidly the network
connection breaks down after few seconds (10-20) and remote
server is not accessible (also not for windows tools). The problem
is hard to reproduce (often is everything working fine).

Following script illustrates the problem:

#!/bin/sh
while true
do
      t=`grep foo /cygdrive/n/path/to/network/file`
done

The problem persists also for 'n:/path...' filename form. If I add
a 'sleep 1' command inside the loop or execute script on local
drive everything is ok.

Thanx for any help,
and sorry if the question is off-topic,
Ljubo


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