Date: Wed, 27 Nov 1996 16:39:07 +0000 From: Verdell Hicks <verdell@novalink.com> To: freebsd-isp@freebsd.org Subject: INN Message-ID: <329C6EAB.2D1E@novalink.com>
next in thread | raw e-mail | index | archive | help
Good Afternoon,
Using INN and wanted to ask a few questions. My history file
has
really gotten screwed up and I can't seem to sync things up again. I
brought the entire sytem down ran makeactive and makehistory and still
when I connect to my news feed I still get a lot of can't symlink this
to that. I've been through the faq and have tried the
ctlinnd renumber ''
makehistory -buv
ctlinnd renumber ''
and it still did not work. First my expire file reads
/remember/:5
## Keep for 1-10 days, allow Expires headers to work.
## for now, expire everything quickly....2 days
*:A:1:3:4
## For alt binaries, expire them in 1 day
alt.binaries.*:A:1:2:2
## Some particular groups stay forever.
#dc.dining*:A:never:never:never
#uunet*:A:never:never:never
Yet it doesn't seem to expire the articles when my hard drive gets down
to 40%. It stops right there. I don't seem to get any error messages
concerning expire. Anyhow, in order to sync things up again I read that
you can simply reformat your news spool and let INN recreate all of the
directories again as the news comes in. What other files will I need to
delete in order to keep this process from blowing up in my face ie.
should I after formatting rerun makeactive and makehistory? should I
actually delete my old history file and let INN start that over also
(will it?). Does anyone have any pointers for me before I reformat and
totally screw things up more?
Thanks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?329C6EAB.2D1E>