Thank you for your suggestions. We are running "windump" (Windows version of
tcpdump) on Windows side as well as "tcpdump" on Linux side - I am not good
at analyzing these - what abnormalities should I be looking for in these ?
...some patterns - I will really appreciate help on these. So far I failed
to see problems.

Also I looked at curl trace files (option --trace <file>)- it is always gets
overwritten for each new session (instance of curl.exe) - is it possible to
have them append to the same file (sort of "trace log" file)? Information in
these are much easier to read.

This is a very good question on which level problem occur - we do not know
it yet. I have doubts that it is happening in the kernel (I could be wrong)
- it looks to me somewhere higher close or on the application level - that
is why I am wondering about curl "internals" - nothing could be ruled out at
this point. Problem looks random and while several processes may be hanging
others may be working fine.

Yuri

-----Original Message-----
From: curl-users-bounces_at_cool.haxx.se
[mailto:curl-users-bounces_at_cool.haxx.se] On Behalf Of Gisle Vanem
Sent: Saturday, November 13, 2004 12:23 PM
To: curl tool talk
Subject: Re: curl processes hang on windows 2003

"Yuri" <yurim_at_shaw.ca> wrote:

> "I/O Writes" is the number of write input/output operations generated
> by a process including file, network and device I/Os (not including
> console operations).

"I/O Writes" is not a very reliable indication of what's going on. And on
what level does this I/O apply? In Winsock's recv/send? Or in the kernel at
the tcpip.sys border. Remember several send() calls may be merged into one
I/O call lower down.

Try to trace the connection with a networks sniffer like Ethereal, tcpdump
etc. That's a far more reliable tool than TaskManager.

--gv
Received on 2004-11-13