No subject

534 	        { "send_timeout", tweak_timeout, &master.send_timeout, 0, 0,
535 	                "Send timeout for client connections. "
536 	                "If no data has been sent to the client in this
many seconds, "
537 	                "the session is closed.\n"
538 	                "See setsockopt(2) under SO_SNDTIMEO for more
information.",
539 	                DELAYED_EFFECT,
540 	                "600", "seconds" },

Yep, the description SHOULD be fixed some day :)
The thing is, the connection **will be** timeouted "send_timeout"
seconds after it has been set, with or without real network activity.
It is, even if the user is receiving data, the connection will be
closed in "send_timeout" seconds.

From:
SOCKET(7)                  Linux Programmer=92s Manual                 SOCK=
ET(7)

       SO_RCVTIMEO and SO_SNDTIMEO
              Specify the receiving or sending  timeouts  until  reporting =
 an
              error.  The argument is a struct timeval.  If an input or out=
put
              function blocks for this period of time, and data has been  s=
ent
              or  received,  the  return  value  of  that function will be =
the
              amount of data transferred; if no data has been transferred  =
and
              the  timeout has been reached then -1 is returned with errno =
set
              to EAGAIN or EWOULDBLOCK just as if the socket was specified =
 to
              be  non-blocking.   If  the timeout is set to zero (the defau=
lt)
              then the operation  will  never  timeout.   Timeouts  only  h=
ave
              effect  for system calls that perform socket I/O (e.g., read(=
2),
              recvmsg(2), send(2), sendmsg(2)); timeouts have  no  effect  =
for
              select(2), poll(2), epoll_wait(2), etc.

Regards,
--=20
Rog=E9rio Schneider

MSN: stockrt at hotmail.com
GTalk: stockrt at gmail.com
Skype: stockrt
http://stockrt.github.com