Hallo, I've run texpire with the appended patch to texpire.c which adds some new debugging statements, .and found one foule groupexpire statement. groupexpire = *.test 2 Shouldn't this glob(7) expression match names like "news.test" only? It matched against most (?all) group names. Examples are: [ new log statements with *.text ] lookup_expire: group alt.comp.sys.palmtops.hp matches *.test expire=1002123510 [ new log statements without *.test ] lookup_expire: group comp.lang.c++.moderated matches comp.lang.* expire=993656551 texpire[3126]: expiregroup: group comp.lang.c++.moderated, expire=993656551 texpire[3126]: comp.lang.c++.moderated: expire 993656551, low water mark 42, high water mark 5856 texpire[3126]: 4820 xover error: Reference does not start with <. texpire[3126]: 4840 xover error: Reference does not start with <. texpire[3126]: 4898 xover error: Reference does not start with <. texpire[3126]: 5142 xover error: Reference does not contain @. texpire[3126]: 5168 xover error: Reference does not contain @. texpire[3126]: 5234 xover error: Reference does not contain @. texpire[3126]: comp.lang.c++.moderated: threads total: 608, to delete: 0 which was (with the foule glob expression) texpire[2890]: comp.lang.c++.moderated: threads total: 608, to delete: 584 So the expire time was set to 2 days .... which explains why most articles where expired ! ## # Expiring+Active handling = 264 debugmode=264 Mit freundlichen Grüßen Volker Apelt -- Volker Apelt volker_apelt .@. yahoo.de (remove the dots, please) Dipl. Chem. +49 6172 31126 Attachment: texpire.c.with_expire_debugging.dif
Attachment:
bin00003.bin
Description: "Description: Binary data"