Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!in-news.erinet.com!newsfeeder.sdsu.edu!newspump.sol.net!spool.mu.edu!usenet.eel.ufl.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!newsmaster From: Robert Withrow <bwithrow@baynetworks.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: DAT Hell Date: Tue, 25 Jun 1996 13:54:56 -0400 Organization: Bay Networks, Inc. Lines: 26 Message-ID: <31D027F0.41C67EA6@baynetworks.com> References: <4pvmjj$flb@mercury.mcs.com> <4q0j0s$h0@uriah.heep.sax.de> <31C8A0C4.15FB7483@rwwa.com> <4qgo0o$q31@uriah.heep.sax.de> NNTP-Posting-Host: dino.wellfleet.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) J Wunsch wrote: > > Robert Withrow <witr@rwwa.com> wrote: > > > > bump the > > > 300000 to something that makes the operation safe for you. Once you > > > found it, multiply it by 2, and use /usr/bin/send-pr to submit your > > > new value so we can integrate it into the driver. > > > > But gee. Isn't there some better way of doing this, like > > a system variable or something? Otherwise, why isn't > > infinity a good value? > > SCSI timeouts are similar tradeoffs like all other timeouts. If you > make them too short, they might still be to short in case the resource > was actually still available, but slow to respond. If you make it > large, it will hang your system for a long time. Yes, but what I am saying is ``isn't there a better way than tweaking the code?'' You didn't comment o the system variable approach. -- Robert Withrow -- (+1 508 436 8256) BWithrow@BayNetworks.com