This does make sense. I do some work on a mail server and I don't use
keepalives because 2 hours is _too_much_ time to be wasting a descriptor.
I periodically check how long a connection has been open and if it exceeds
a certain amount I close the connection.
-Kip
On Tue, 1 Jun 1999, David Schwartz wrote:
>
> I think he was suggesting that the apps close the connection if they
> receive no data from some amount of time. (Isn't this common sense?)
>
> DS
>
> > On Tue, Jun 01, 1999 at 01:30:31PM -0700, Julian Elischer wrote:
> >
> > > maybe we should fix our SERVER apps..
> > > e.g. telnetd, sshd, etc. to have 1 week timeouts
> >
> > IIRC, it is not possible to specify how long the keepalive interval
> > should be, using the socket interface. Do you suggest we add a new
> > interface not present in other Unix implementations, or that we make
> > SO_KEEPALIVE always have a one-week timeout, surprising the other
> > applications that expect it to be faster?
> >
> > Both of these seem remarkably unappealing to me.
> >
> > Matt
> >
> > --
> > Matthew Hunt <[email protected]> * Inertia is a property
> > http://www.pobox.com/~mph/ * of matter.
> >
> >
> > To Unsubscribe: send mail to [email protected]
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
>
>
> To Unsubscribe: send mail to [email protected]
> with "unsubscribe freebsd-current" in the body of the message
>
>
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
