Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!bu-cs!purdue!i.cc.purdue.edu!h.cc.purdue.edu!s.cc.purdue.edu!ain
From: ain@s.cc.purdue.edu.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: comp.binaries.amiga (was Re: Picture swap)
Message-ID: <3246@s.cc.purdue.edu>
Date: 23 Jun 88 17:06:04 GMT
References: <8806161902.AA16559@cory.Berkeley.EDU> <417@jc3b21.UUCP> <2827@umd5.umd.edu> <9701@g.ms.uky.edu> <1462@teksce.SCE.TEK.COM>
Reply-To: ain@s.cc.purdue.edu.UUCP (Patrick White)
Distribution: na
Organization: PUCC Land, USA
Lines: 23

In article <1462@teksce.SCE.TEK.COM> dales@teksce.SCE.TEK.COM (Dale Snell) writes:
>...  But if everybody who normally
>collects the binaries calls in, won't they be overloaded?  I don't have
>enough data to make even a halfway decent guess.  (Pat?  Somebody?)  

   I'm not actually in on the system stuff around here, but I do know a bit
about the system the archives are on:  j.cc... is a dualed vax 780 and it's
load is 10-15 during normal working hours, (1-3 late at night)...  If
everybody were calling it, it's load would probably go up enough that the
service would be discontinued (at least when people are using it -- it's
the staff machine around here, so there is always someone using it).
   Of course, the whole point is moot right now since the machine does not
have a uucp connection (we use ee.ecn... -- hence the mailing-binaries and
posting-volume restrictions).

   Therefore, I am in favor of keeping the binaries groups.. but the decision
certainly isn't up to me :-)


-- Pat White   (co-moderator comp.sources/binaries.amiga)
ARPA/UUCP: j.cc.purdue.edu!ain  BITNET: PATWHITE@PURCCVM  PHONE: (317) 743-8421
U.S.  Mail:  320 Brown St. apt. 406,    West Lafayette, IN 47906
[How do you get to heaven?   Go to Pluto and hang a left.]