On Sun, Nov 22, 2009 at 10:44 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
On Thu, Nov 19, 2009 at 10:02 PM, Mike Christie micha...@cs.wisc.edu wrote:
Ulrich Windl wrote:
On 19 Nov 2009 at 11:07, Erez Zilber wrote:
On Thu, Nov 19, 2009 at 9:38 AM, Ulrich Windl
On Tue, Dec 1, 2009 at 2:57 PM, Erez Zilber erezzi.l...@gmail.com wrote:
On Sun, Nov 22, 2009 at 11:24 PM, Erez Zilber erezzi.l...@gmail.com wrote:
On Sun, Nov 22, 2009 at 10:44 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
On Thu, Nov 19, 2009 at 10:02 PM, Mike Christie
On 1 Dec 2009 at 14:57, Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what caused
it to be so slow on that specific time, you can see if your
network was very
On Tue, Dec 1, 2009 at 3:16 PM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
On 1 Dec 2009 at 14:57, Erez Zilber wrote:
Maintain a list of nop-out PDUs that almost timed out.
With this information, you can understand and debug the
whole system: you can check your target and see what
Hi all,
I'm a CS student and I'm trying to understand and locate the source
code for iSCSI connection establishment. But I encountered the
following problem. Could anyone maybe show me where I should go? Any
help would be highly appreciated!!
1. I searched in the entire open-iscsi project and
Ulrich Windl wrote:
On 24 Nov 2009 at 13:20, guy keren wrote:
[...]
by the way - if the system is set to generate core files for daemons,
then at least in theory it is possible to write some gdb macros that
will extract the non-flushed part of the logs from the core file -
assuming the
