I'm using nntpcache 2.4.0b3 on an HP-UX system. My entry in nntpcache.config for maxArtAge is 2w. However, I'm seeing that expire is running as soon as a client re-connects. The message in my syslog file looks like: Feb 29 12:58:40 nntpcache-expire[13405]: expire.c:211: usedblocks = 70.2%, \ usedinodes = 30.5%, maxArtAge = 41s, expire ended My other entries related to expire are set to the following values: # run expire if there are under this number of inodes in the cache partition minFilesFreePercent 10 # expire if there are under this number of blocks free in the cache partition minBlocksFreePercent 10 # check disk space, etc for automatic expiry this often # (but only after a client connects or disconnects) expireCheckPeriod 5m Any idea what is triggering expire to run? Thanks. Bruce +----------------------------------------------------------------+ | Bruce Hauge | | AGILENT TECHNOLOGIES EMAIL: bruce_hauge@agilent.com | | Imaging Electronics Division PHONE: (541) 715-2675 | | 1000 NE Circle Blvd., MS: 133A FAX: (541) 715-8930 | | Corvallis, OR 97330 | +----------------------------------------------------------------+
