Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!picard.eng.ohio-state.edu!keith From: keith@picard.eng.ohio-state.edu (Keith M Boyer) Newsgroups: comp.sys.hp Subject: Re: why do cluster clients panic after cluster servers die Message-ID: <81092@tut.cis.ohio-state.edu> Date: 1 Jun 90 16:17:22 GMT References: <7752@rasp.eng.cam.ac.uk> <1720008@hpbbi4.HP.COM> Sender: news@tut.cis.ohio-state.edu Reply-To: Keith M Boyer Organization: The Ohio State University Dept of Computer & Information Science Lines: 25 In article cph@zurich.ai.mit.edu (Chris Hanson) writes: >It seems to me that the diskless protocol could be extended in an >upwards-compatible way so that the client supplied the necessary >information to the server to permit resynchronization when the server >had lost the information for one reason or another. Certainly the >client knows all of the relevant state, such as what files are open. > >A little cleverness in the design of this software could eliminate a >lot of headaches for customers. While I would also like to see the clients behave more robustly I can see that the problems of true resynchronization might be difficult. In our environment here at OSU it would be Damn Nice if the client would AT LEAST try to reboot automatically after it fails. We have approx. 80 HP workstations in 5 different locations. Having to walk from one building to another to cycle power is a best, inconvienient. ++keith -=- - Keith M. Boyer Department of Computer and Information Science -- THE Ohio State University 2036 Neil Ave. Columbus OH USA 43210-1277 - keith@cis.ohio-state.edu or ...!osu-cis!cis.ohio-state.edu!keith EVERYTHING SHOULD BE MADE AS SIMPLE AS POSSIBLE,BUT NOT SIMPLER-Albert Einstein