2.3exp: expire and tradspool
John P Speno
speno at isc.upenn.edu
Fri Aug 20 17:19:01 UTC 1999
I'm trying to get different expiration times for different tradspool stored
newsgroups.
I see that newsgroup based expire doesn't yet work in 2.3exp. It looks like
storage class based expire is supposed to work, but either it doesn't, or I'm
not doing something right (I hope the later).
For example, my storage.conf looks like this:
method tradspool {
newsgroups: upenn.law.announcements
class: 10
}
method tradspool {
newsgroups: upenn.test
class: 14
}
method cnfs {
newsgroups: alt.binaries.*,alt.mag.playboy,comp.binaries.*,relcom.comp.binaries,fj.binaries.*,it.binari.*,alt.fan.snuffles
class: 0
options: BINARIES
}
method cnfs {
newsgroups: alt.*
class: 1
options: ALT001
}
method cnfs {
newsgroups: control.*
class: 2
options: CON001
}
method tradspool {
newsgroups: *
class: 3
}
And my expire.ctl is:
/remember/:14
# default
3:1:2:4
# upenn.test
14:.1:.1:.1
And during expire last evening, expire.list contained 2787966 tokens, and
expire.log contained the exactly the same number of these lines:
Class definition 0 is missing from control file, assuming zero expiration
Which would seem to indicate that expire treated all articles as if they
were in class 0.
So, it is the case that even the storage class based expire doesn't yet
work? If so, what needs to be done to fix this?
I assume that the storage class number needs to be in the storage token?
Thanks.
More information about the inn-workers
mailing list