| Summary: | Lost artikles with delaybody | ||
|---|---|---|---|
| Product: | [Unmaintained] knode | Reporter: | Unknown <null> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.6.1 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
fnoack
2001-09-27 20:16:42 UTC
Hello ! It seems that I have the same bug ! Systeminformations: Suse 7.3 Linux Kernel: 2.4.10 KDE 2.2.1 Knode 0.6.1 leafnode 1.9.19 Nothing is compiled by myself everything are RPMs of my Distribution ! regards Kim Neunert knode looks for the Xref: header set by leafnode. After fetching the news via fetchnews all old articles have got a new Xref: header with a new number so that knode can't get it from the news server leafnode. Why doesn't use knode the message ID? This should stay consistent. -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net Can you please give us an updated on whether this is still a problem for either of you with a more recent version of knode? Knode 0.7.1 and Leafnode 1.9.25.rel misbehave when delaybody=1. SuSE 7.0 KDE 3.0.4 kernel 2.2.19 Knode now works with the leafnode option of delaybody=1 if the new leafnode option of delaybody_in_situ=1 is set int /etc/leafnode/config I am using; leafnode-1.9.41-1mdk Knode 0.7.2 KDE 3.1.4 Mandrake cooker Is it reasonable to close this bug as FIXED? or as WONTFIX? Rainer Neither. I will fix it. There is a workaround for now, though.
Besides setting delaybody=1 in Leafnode's configuration, also set the option below:
delaybody_in_situ = 1
Then go to Settings -> Configure KNode -> Reading News -> Memory Consumption and set the "Cache size for articles" to 0KB. That should do it.
Replaced fnoack@t-online.de with null@kde.org due to bounces by reporter Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. |