×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Fri, 27 Feb 2009, Scott Klement wrote:
Interesting. Do you know what it actually does, under the covers?
Obviously it's sending some data... but what data can it send that won't
muck up the session?
I suppose you won't know this... :( I'll have to sniff the connection
to find out
Interesting to note that I usually have the exact reverse problem:
Windows Client Access sessions drop but tn5250 marches on perfectly.
In linux there are three tcp keepalive settings: tcp_keepalive_intvl,
tcp_keepalive_probes, and tcp_keepalive_time in /proc/sys/net/ipv4 (at
least there are on kernel 2.6.24.5). Might these be something like what
you are looking for? I thought I remembered seeing an option to
setsockopt that would set the tcp keepalive per socket but a quick review
of the man page turns up nothing (other than referencing the /proc
settings I listed above).
James Rich
if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
