Re: tcptrace Connections set to INACTIve after 4 minutes idle time.

From: Steve Bonds (yf99knh02@sneakemail.com)
Date: 03/12/03

  • Next message: Brian Utterback: "Re: tcptrace Connections set to INACTIve after 4 minutes idle time."

    Date: Wed, 12 Mar 2003 16:58:21 -0800 (PST)
    From: "Steve Bonds" <yf99knh02@sneakemail.com>
    Subject: Re: tcptrace Connections set to INACTIve after 4 minutes idle time.
    Message-ID: <27311-19409@sneakemail.com>
    
    

    It looks like the current CVS version already has this as the
    nonreal_live_conn_interval option. Must have missed that in the mailing
    list archive as I was searching through it.

    Sorry for the noise. ;-)

      -- Steve

    On Wed, 12 Mar 2003, Steve Bonds yf99knh02-at-sneakemail.com |tcptrace| wrote:

    > This same undocumented feature just bit me as well. Attached is a patch
    > to completely remove the 4 minute limit.
    >
    > If I get real motivated, I might make a nicer patch that allows one to set
    > the timeout as a command line option.

    ----------------------------------------------------------------------------
    To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
    majordomo@tcptrace.org.



    This archive was generated by hypermail 2b30 : 03/13/03 EST