Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!hao!oddjob!gargoyle!jpusa1!news
From: news@jpusa1.UUCP
Newsgroups: comp.unix.questions,news.sysadmin
Subject: uuxqt problems with news
Message-ID: <301@jpusa1.UUCP>
Date: Sat, 13-Jun-87 12:42:10 EDT
Article-I.D.: jpusa1.301
Posted: Sat Jun 13 12:42:10 1987
Date-Received: Sat, 13-Jun-87 23:56:20 EDT
References: <116@bvax.UUCP> <311@pollux.UUCP> <748@van-bc.UUCP> <287@l5comp.UUCP>
Reply-To: stu@jpusa1.UUCP (Stu Heiss)
Followup-To: comp.unix.questions
Distribution: na
Organization: JPUSA - Chicago, IL
Lines: 36
Xref: utgpu comp.unix.questions:2467 news.sysadmin:207

Summary:
Expires:

In article <287@l5comp.UUCP> scotty@l5comp.UUCP (Scott Turner) writes:
-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. 
You should turn on spooling to cut down on uucp time.  What's going on is uuxqt
is firing up news with the associated compress/batch stuff and the machine is
bogging down.  Much better to let uucp squirel away the batches to be processed
later.  I use batching and if the uucp port is active, I don't start the unbatch.
This is handled in a script run hourly by cron.
-
-The system was still running the expire AND the rnews -U at 13:00.
News 2.11 handles the expire/rnews interlocking so this shouldn't be a problem.
At the end of expire, an 'rnews -U' is started up so it's normal to see this.
-As a side issue, is it 'safe' to kill -9 an active expire?
You'll probably trash your history file if you do.  Use an 'expire -r' to fix it.
-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?
Separating the uuxqt from news via spooling is what's needed.  I also don't
start up expire if news or the uucp port are active.  The expire.sh script
checks for this and sleeps 5 min till things have quieted down.  This is more
to keep the load down than rnews/expire paranoia as the interlocking seems to
work now.
-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.
You can hack Pnews but anyone who knows how can post an article even if you have
no news connections or news software.

Stu Heiss {gargoyle,ihnp4}!jpusa1!stu