I'm just speculating, but I'd guess it was previously set to 60. At some point, someone suspected that 60 minutes was synching with something else, so they changed it 1 minute just so ours would be different.
-----Original Message-----
From: Christopher Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx]
Sent: Wednesday, July 25, 2018 3:54 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: TCP/IP timeouts
Odd number and thank you for sharing.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Wednesday, July 25, 2018 1:42 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: TCP/IP timeouts
Ours is 59. I have no recollection as to when/why it was set.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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
