Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!ut-sally!utah-cs!utah-gr!stride!l5comp!scotty
From: scotty@l5comp.UUCP
Newsgroups: comp.unix.questions,news.sysadmin
Subject: Re: uuxqt problems with news
Message-ID: <287@l5comp.UUCP>
Date: Tue, 9-Jun-87 19:49:57 EDT
Article-I.D.: l5comp.287
Posted: Tue Jun  9 19:49:57 1987
Date-Received: Sat, 13-Jun-87 11:15:35 EDT
References: <116@bvax.UUCP> <311@pollux.UUCP> <748@van-bc.UUCP>
Reply-To: scotty@l5comp.UUCP (Scott Turner)
Distribution: na
Organization: L5 Computing, Edmonds, WA
Lines: 55
Keywords: news, UniStride 2.1, HELP!
Xref: utgpu comp.unix.questions:2460 news.sysadmin:205
Summary: uuxqt questions, PLUS how do I protect myself from comp.sources.misc

First, some further questions about uuxqt and the news.

I get my news by calling in for it to a remote site. The remote site batches it
and sets it up to be processed by cunbatch on my system.

I have spooling turned on in my news stuff. I also have nice set.

Uuxqt still runs for a good hour after the actual uucp operation finishes. 
I've also noticed that articles get posted onto my local system while uuxqt is
running. I suspect that after the first file is decompressed news starts 
running and posting begins. This has to slow down further de-compressing.
Which also of course lengthens the time that uuxqt is left active.

Do I have some switch set wrong in my system?

Second, there be time slot hoppers in the world. I have an assigned dial in
time, but every so often someone jumps it. Last week my system didn't get
through till 05:00 (time slot was at 02:00) one night and then didn't
finish uucp till 06:30. However, I have an expire-daily that runs at 06:00.
The system was still running the expire AND the rnews -U at 13:00.

I assume this was a result of expire running at the same time as news was
being munched down, BUT I don't know enough about the news system to say
for sure. I had to kill -9 the rnews -U at 13:20 to shut everything down.
The pacct files had run up to 2.6 megs so I figured something was fatally
wrong. :)

As a side issue, is it 'safe' to kill -9 an active expire?

Was the expire-daily the problem? And if so what should I do to prevent
this mess from happening again? Move expire-daily till MUCH further past
the 02:00 news feed slot?

Third, I'm sure everyone here has seen the 'rebel approved' posting to
comp.sources.misc. Is there anything I can do to the news software on my
system to prevent someone posting such a message using my system? I know
trust is a great protection against alot of stuff, and I DO trust my
regular users, but that posting seems to have been made from a 'guest'
account (if that wasn't faked as well.) I'd rather build in protection than
yank the guest account on my system.

And to whomever made that posting: You should have signed it rather than
skulking around like a criminal with a mask on. Your efforts are more
likely to focus attention on locking the system up rather than on
unmoderating newsgroups. When I read your posting there was an answering
pang of rebellion in my heart, then I looked to see whom to converse with
and my heart froze as cold as the ice in Siberia.

Thanks in advance for any help,

Scott Turner
-- 
UUCP-stick: stride!l5comp!scotty | If you want to injure my goldfish just make
UUCP-auto: scotty@l5comp.UUCP    | sure I don't run up a vet bill.
GEnie: JST			 | "The bombs drop in 5 minutes" R. Reagan
		Disclaimer? I own L5 Computing. Isn't that enough?