[news.software.b] Need help with CNews expire

asklingl@medusa.informatik.uni-erlangen.de (Andreas Klingler) (08/31/90)

I just switched from Bnews to CNews on this system (a Sequent running
DYNIX) and I am having severe trubble with expire:

If cron starts Doexpire I get a mail with hundreds of lines like this:

expire: can't archive `comp/os/os9/985' (No such file or directory)

The thing is this article _does_ exist. Even worse, if I start
Doexpire manually with exactly the same environment as cron does
all goes fine. 
Well allmost all. Expire expires only some articles for which it is
now time to go away but leaves the ones mentioned in the mail
(and all older ones) alone. So my news-partition if filling up with
old articles. -> HELP!!!

I am running CNews with the patch of 25 May 1990.

All help appreciated (Please send E-Mail).

	Andy

henry@zoo.toronto.edu (Henry Spencer) (09/02/90)

In article <3087@medusa.informatik.uni-erlangen.de> asklingl@medusa.informatik.uni-erlangen.de (Andreas Klingler) writes:
>expire: can't archive `comp/os/os9/985' (No such file or directory)
>
>The thing is this article _does_ exist...

The message probably is referring not to the article, but to the place
where it is supposed to be archived.  Something is going wrong with
directory creation for archiving (perhaps the top-level archive directory
is not owned by news?).
-- 
TCP/IP: handling tomorrow's loads today| Henry Spencer at U of Toronto Zoology
OSI: handling yesterday's loads someday|  henry@zoo.toronto.edu   utzoo!henry

edhew@xenitec.on.ca (Ed Hew) (09/05/90)

In article <3087@medusa.informatik.uni-erlangen.de> asklingl@medusa.informatik.uni-erlangen.de (Andreas Klingler) writes:
>Well allmost all. Expire expires only some articles for which it is
>now time to go away but leaves the ones mentioned in the mail
>(and all older ones) alone. So my news-partition if filling up with
>old articles. -> HELP!!!
>	Andy

Totally aside from Henry's (very valid) comment on ownership of
the news spool hierarchy, we run the following crontabs line from
the root crontabs file, "just in case" (be *very* careful of the
directory source point):

40 5 * * 1	find /usr/spool/news -ctime 60 -print -exec rm {} \; |mail -s "rm mouldy news" sys

If you're not running SCO UNIX (with it's C2 level security turned
on) as we are, then you can probably do it from the uid=news
crontabs file (preferable).

Note that on our site in the months since we put this line in,
I don't recall that it's ever actually found anything to rm,
but it may help you as an emergency measure (adjusted to whatever
ageing factor you desire).  Also, this suggestion doesn't solve
your actual problem, merely alleviates the symptoms.

  Ed. A. Hew      SCO Authorized Instructor      XeniTec Consulting Services
  edhew@xenitec.on.ca  | ..!{watmath|lsuc}!xenitec!edhew   |  (519) 570-9848
	   (sco.opendesktop newsgroup <=> mlist gateway maintainer)