Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!think.com!mintaka!wookumz.ai.mit.edu!entropy From: entropy@ai.mit.edu (entropy) Newsgroups: comp.sys.atari.st Subject: Re: Bye Bye BART Message-ID: Date: 19 Feb 91 19:51:52 GMT References: <4484@syma.sussex.ac.uk> <1991Feb17.235832.17444@msuinfo.cl.msu.edu> <2798@krafla.rhi.hi.is> <1991Feb19.154407.4016@math.lsa.umich.edu> Sender: daemon@mintaka.lcs.mit.edu (Lucifer Maleficius) Organization: /home/fsg/entropy/temporary/.organization Lines: 22 In-Reply-To: brode@math.lsa.umich.edu's message of 19 Feb 91 15:44:07 GMT To: In article <1991Feb19.154407.4016@math.lsa.umich.edu> brode@math.lsa.umich.edu (Jon Brode) writes: - we don't have the administrative time to deal with pseudo-accounts - we can't assume that account names are unique on the internet - there are many, many twisted ways to write valid addresses - some networks use user@host.domain instead of user@domain - some systems let users change their mail names independent of acct name I haven't been following this thread very closely because I didn't use BART. But as I understand it, someone dowloaded more than his fair share, which caused too much of a strain on the system, and caused someone in administration to shut it down. Why not just put an upper limit on the amount of resources BART is allowed to use? Like, only allow it to send 10 files an hour, or perhaps run it at a really low priority, or something like that. Then if some idiot _does_ break security and grab hundreds of megs of stuff with one request, the worst that can happen is everyone else has to wait a few hours (or perhaps days) and then get their files. This would probably require some tuning to prevent too much backlog, but it certainly would prevent an irresponsible user from getting the system shut down again. entropy