Xref: utzoo comp.sources.d:4023 comp.mail.uucp:3499
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!sequent!ccssrv!perry
From: perry@ccssrv.UUCP (Perry Hutchison)
Newsgroups: comp.sources.d,comp.mail.uucp
Subject: Re: Somebody invoked uucico -x9 to osu-cis...
Message-ID: <609@ccssrv.UUCP>
Date: 8 Sep 89 22:49:38 GMT
References: <KARL.89Sep7225153@kant.cis.ohio-state.edu>
Reply-To: perry@ccssrv.UUCP (Perry Hutchison)
Organization: Control-C Software, Inc., Beaverton, OR
Lines: 20

In article <KARL.89Sep7225153@kant.cis.ohio-state.edu>
karl@kant.cis.ohio-state.edu (Karl Kleinpaste) writes:

> And then someone out there had the unmatched _gall_ to request the
> whole of GNU Emacs source with uucico running -x9.
>
> For those of you not familiar, the -x option to uucico invokes debugging ...
> invoking -x9 at YOUR end also puts MY end into -x9 ... [it generated]
> an audit file well in excess of 18Mbytes.
>
> DON'T DO THAT.  ...  If you must, use -x9 long enough to prove that a
> connection works, or to find a problem.  Don't leave it on when you do
> large software transfers from a public archive site such as osu-cis.

OUCH!!  I trust it was unintentional, or at worst the consequences were
unforseen.

By way of preventing such incidents in the future, it sounds to me like
uucico could be patched such that setting -x does _not_ automagically put
the _remote_ end into -x mode.