Fix NopInInterval README info to show that a NOP-In will timeout

when NopInTimeout seconds and not the RspTimeout seconds has passed
without getting a response.

Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>



git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@5094 d57e44dd-8a1f-0410-8b47-8ef2f437770f
This commit is contained in:
Vladislav Bolkhovitin
2013-11-09 03:21:19 +00:00
parent 13ee8e1649
commit 388cb01060
2 changed files with 2 additions and 2 deletions

View File

@@ -305,7 +305,7 @@ Each target subdirectory contains the following entries:
- NopInInterval - defines interval between NOP-In requests, which the
target will send on idle connections to check if the initiator is
still alive. If there is no NOP-Out reply from the initiator in
RspTimeout time, the corresponding connection will be closed. Default
NopInTimeout seconds, the corresponding connection will be closed. Default
is 30 seconds. If it's set to 0, then NOP-In requests are disabled.
- NopInTimeout - defines the maximum time in seconds a NOP-In request

View File

@@ -139,7 +139,7 @@ Each target subdirectory contains the following entries:
- NopInInterval - defines interval between NOP-In requests, which the
target will send on idle connections to check if the initiator is
still alive. If there is no NOP-Out reply from the initiator in
RspTimeout time, the corresponding connection will be closed. Default
NopInTimeout seconds, the corresponding connection will be closed. Default
is 30 seconds. If it's set to 0, then NOP-In requests are disabled.
- NopInTimeout - defines the maximum time in seconds a NOP-In request