From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 29 Jun 2007 23:32:48 +0200 From: Enrico Weigelt To: 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 ? Message-ID: <20070629213248.GA7109@nibiru.local> References: <20070629141216.GA27541@nibiru.local> <20070629201330.GA17817@nibiru.local> <8ccc8ba40706291330y69c29a49w55c74b8c96477f00@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8ccc8ba40706291330y69c29a49w55c74b8c96477f00@mail.gmail.com> User-Agent: Mutt/1.4.1i Topicbox-Message-UUID: 8c2fbbd0-ead2-11e9-9d60-3106f5b1d025 * 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 ? > I had to adjust timeouts in the Plan B ns (which does timeout as you > suggest) a lot of times, to avoid paranoia regarding "is it a network > error, or yet another bug I introduced?". > > You can use an intermediate file server process to do your timeouts, > and run them only when you know there's a problem. That way the kernel > you never see a hanged up ns. Aehm, are we still talking about the v9fs linux driver ? It really shouldn't hang up if the server dies. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------