From mboxrd@z Thu Jan  1 00:00:00 1970
From: Micah Stetson <micah@cnm-vra.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio and acme scrolling
Message-ID: <20040327202713.GB20944@epaphras.cnm-vra.com>
References: <20040327050754.GA20193@epaphras.cnm-vra.com> <466a2993c3a0232a58065be590e2a716@plan9.bell-labs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <466a2993c3a0232a58065be590e2a716@plan9.bell-labs.com>
User-Agent: Mutt/1.4.1i
Date: Sat, 27 Mar 2004 12:27:13 -0800
Topicbox-Message-UUID: 4503c60c-eacd-11e9-9e20-41e7f4b1d025

> The clock (timer 2) speeds up by a factor of 5 or so.

I think this might also explain another problem I've had.
Sometimes, when I've booted from the fileserver using
IL, my laptop will work fine for a while and then decide
that the fileserver connection has hung up.  Running
netstat on the server says it's still established.  This
has happened 2 or 3 times in as many days, and, if I
remember correctly, always after a screen blank.  I
haven't noticed it using TCP, but I've only booted with
TCP once or twice.  I'm thinking the factor five speedup
is causing a race between the 30 second keep-alive timer
and the 6-second delay before a query is sent on an
inactive connnection.  When the timer wins, the connection
is torn down.

I've also seen a disk error or two recently from fossil
on this machine, as someone else talked about in this
thread.

It's so nice to have something to blame it all on.

Micah