On Mon, 1 Jun 1998, Shayne Hardesty wrote: > Right now my expiration consists of doing a "killall nntpcache", then "rm > -rf /news0/cache", then rm'ing the history and mmap files, then restarting > nntpcache.. kinda sucks to have to do it that way though.. With our > traffic here I'm having to do this once every 2-3 weeks with a 4 gig > cache spool. If you must do that, just kill -USR2 `cat /path/to/nntpcache.pid` > If anyone out there has 2.3.2.1 expiring on a linux server how about > posting to the list and let us know if you've done anything special? Nntpcache happily expires and prunes the history database here (2 separate operations) automatically and I don't believe I'm doing anything special - apart from putting news on its own dedicated partition. One thing I will note however is that while and expire or prune is happening, the server will not accept any new connections. This leads to regular screaming from frustrated users as the proces takes around 20 hours on my setup. AB
