Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!sol.ctr.columbia.edu!caen!news From: todd_strauch@med.umich.edu Newsgroups: comp.protocols.appletalk Subject: Re: Dealing with crashed AppleShare servers Message-ID: Date: 13 Jun 91 16:31:16 GMT Article-I.D.: engin.W9B-KZ References: <1991Jun12.183719.16226@phri.nyu.edu> Organization: University of Michigan Medical School Lines: 22 In article <1991Jun12.183719.16226@phri.nyu.edu> roy@alanine.phri.nyu.edu (Roy Smith) writes: > > We're running AppleShare 2.0.1 on an SE/30 over LocalTalk with a >variety of clients running 6.0.[567]. Many of the clients have the "mount >automatically on reboot" boxes checked in the chooser for the server's >disks. The problem is that if the server has crashed (which seems to >happen periodically), the clients just hang when they are rebooted. If you >disconnect the client from the network while it reboots, it comes up fine. > > Is there anyway to keep the clients from hanging in the face of a >crashed server other than isolating them from the network? The stuff on >the server is not essential, but it's used commonly enough that it's >convenient to auto-mount. Is there some way to specify "try to automount >on reboot, but timeout after 15 seconds" or some such? > Not finding an Appleshare volume on bootup should not cause your client machines to hang. There will be a pause as Appleshare on the client machines makes several attempts to connect to the servers, but the client Appleshare will give up after a brief time period (10 seconds or so). A list of your common cdevs and inits might be enlightening.