At 08:24 AM 12/19/01 +0100, you wrote:
>Somehow i notice that (only some) groups are not cached. This is normal when
>the group hasn't been read for more then 15 days. But on some groups (mostly
>groups which are not frequently read) this is not working ok. For example; i
>have just read a group called rec.parks.theme. The group is very
>incomplete, and does only have a few messages.When i ask dnews if the group
>is cached, it responds;
>
>-> tellnews showcached rec.parks.theme
>200 Welcome to the public newsserver news://news.nb.nu, 5.5d1, S0
>281 Completed
>
>The wating period between the read action and tellnews showcached action is
>more then a few hours.
>So it is not triggered by reading. When i ask dnews to cache it;
>
>-> tellnews cached rec.parks.theme
>200 Welcome to the public newsserver news://news.nb.nu, 5.5d1, S0
>Setting {rec.parks.theme} to cached days
>1 groups cached
>281 Completed
>
>�t is working ok again;
>
>
>-> tellnews showgroups rec.parks.theme
>200 Welcome to the public newsserver news://news.nb.nu, 5.5d1, S0
>[11831:12448] rec.parks.theme start=26769 end=26936 items=168, upto on feed
>0, days 0 Pile 0 1 xov=1 Normal
>281 Completed
>
>
>Is this an error in Dnews? Do i have to upgrade? The strange thing is that
>this only occurs to groups which are read only be one person. Frequently
>vistited groups don't have these problems.
It is likely to be caused by the news client involved, some news clients fail
to trigger caching, you may find if you set in dnews.conf
cache_onxover true
or cache_ongroup true
then it fixes the problem, try the xover one first that's probably enough
to do the trick.
ChrisP.
