Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!inquo!in-news.erinet.com!ddsw1!news.mcs.net!not-for-mail From: tundra@MCS.COM (Tim Daneliuk) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: DAT Hell Date: 25 Jun 1996 21:41:05 -0500 Organization: TundraWare Lines: 34 Message-ID: <4qq801$hml@Mercury.mcs.com> References: <4pvmjj$flb@mercury.mcs.com> <31C8A0C4.15FB7483@rwwa.com> <4qgo0o$q31@uriah.heep.sax.de> <31D027F0.41C67EA6@baynetworks.com> Reply-To: tundra@tundraware.com NNTP-Posting-Host: mercury.mcs.com In article <31D027F0.41C67EA6@baynetworks.com>, Robert Withrow <bwithrow@baynetworks.com> wrote: >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 BTW, the value that finally worked was 12000000 -- ------------------------------------------------------------------------------ Tim Daneliuk / tundra@tundraware.com Voicemail/FAX 847.827.1706