Yeah, that's the way I use it. I schedule it to run at times I expect interactive traffic to be low to cache the headers of twenty or so of the most-read newsgroups. You don't have to use it at all to use nntpcache, so far as I can tell. Newshound just acts like a client process, requesting articles or headers or whatever, so that stuff will be cached _before_ a human comes along to read those groups. Do you have some scenario in mind that you're having trouble setting up? Cheers, -Brian On Wed, 17 Nov 1999, Ian Diddams wrote: > > BMM wrote: > > > > newshound is a client process which requests stuff (articles, headers, > > whatever) from nntpcached, causing that stuff to be cached locally. The > > man page for newshound is fairly descriptive, though I'm still not sure > > what "low, middle, and high" refer to. > > > But what is its status - is it a "must run daily at > nmidnight/hourly/whatever" or is it a sort of "useful tool for helping > with busy newsgroups, probably during quiet hours" ? (of which the > latter sounds more likely to me). > > Cheers > > > > -- > Didds >
