"Robert G. Brown" <rbrown@kalamazoo.net> writes: > Looking at the above file, I see no violations of commenting and so forth, and > I think (especially after putting in a few printf's) that there is a flaw in > the way this commenting stuff is being handled. It isn't documented, but nntpcache.servers /* */ handing is, well, stupid in the extreme. Comment open and closes are only detected on the beginings of lines. This is fixed in the development tree (due out new year). > 1. nntpcache seems to download 'way too much stuff! Now, I know EXACTLY what > my users are reading, since I'm the only user. I use tin to read news, and > I have applications that traverse the tree of directories that hold articles, > sniffing for different things. Also, I used newshound to download whole > groups. I can't speak for newshound, as I know little about how it currently works, but I'm convinced what you are seeing is merely nntpcache cross-post seeding the cache. i.e when an article has been posted in n newsgroups and you read it in 1, nntpcache will create entries for the article in the other news groups. These entries are hardlinks, each of which only takes up an extra inode (which are reserved by the file-system anyway), so appart from the directory names the cross-posting takes up no additional space. > All of this stuff works from lists (tin, my apps, and newshound), so I would > expect that I would have a number of paths equal to the number of news- > groups I'm interested in (around 250). See above. > Newsreaders > =========== > nntpcache does a good job of fooling tin, but it doesn't do such a good job > of fo0ling other readers, like xrn. Any suggestions for a newsreader that > works well with nntpcache (besides tin)? Every thing I've thrown at 1.0.7.1 seems to work (tin, slrn, nn, gnus, trn). There has been a single report of Netscape-4 having problems. Can you provide nntpcache syslog output for xrn? > I also notice that when I break my ppp link, tin will sometimes lock up, > even though I know (by watching newshound and the resulting directory) tha > the newsgroup I want to read is completely cached. I see no reason why we > can't use nntpcache as a server for readers, even though it's not on-line > to the servers listed in the servers file. The problem here is that nntpcache tries very hard to provide up-to-the-minute news and the default high-water-mark check timeout reflects this. I agree having an option to continue serving from the cache in the face of server errors is probably a good idea though... though it requires caching of server errors - but this can be done on an nntpcached wide basis. > While I do not subscribe to the nntpcache mailing list > (mostly due to what seems to be domain migration on your part), I plan to > do this in the next 24 hours. Sorry if some of these issue may duplicate > what's already been discussed on the mailing list, but I'm looking forward > to some response from you(even if it's pointers to the mailing list archives). > > Thanks and Regards, > ---> RGB <--- nntpcache-users-request@nntpcache.org is what you want. Cheers, Julian.
