From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <13426df10706291440k5cd28d15r1077311276ec9d18@mail.gmail.com> Date: Fri, 29 Jun 2007 14:40:15 -0700 From: "ron minnich" To: weigelt@metux.de, "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] What do I need for a small 9P2000 server @ Linux ? In-Reply-To: <20070629213248.GA7109@nibiru.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070629141216.GA27541@nibiru.local> <20070629201330.GA17817@nibiru.local> <8ccc8ba40706291330y69c29a49w55c74b8c96477f00@mail.gmail.com> <20070629213248.GA7109@nibiru.local> Cc: Topicbox-Message-UUID: 8c33da12-ead2-11e9-9d60-3106f5b1d025 On 6/29/07, Enrico Weigelt wrote: > * Francisco J Ballesteros wrote: > > > Another problem is that in general, only the user or the application > > knows when it's a problem, and when it's a s l o o w link. > > No keepalive / ping to check network problems ? in the good old days of tcp/ip over radio, there were links that went silent for days in some cases, then continued. SO: > It really shouldn't hang up if the server dies. if the server is half a world away, how do you know if it's dead? I think in the limit this is a tough problem. ron