Thread: [Noffle-users] Marked for Download Problem
Brought to you by:
bears
From: Andre B. <and...@we...> - 2004-03-31 08:42:21
|
Hi there, I see a strange behavior in noffle 1.1.5: articles Marked for Download are never fetched. In the first place, I don't understand why there are such articles anyway. I'm on modem dialup, and my /etc/ppp/ip-up contains "noffle -n && noffle -f", my /etc/ppp/ip-down "noffle -o". My newsreader is set up to fetch articles from localhost every five minutes, it's run from fetchmail as postconnect command. -Andre |
From: Jim H. <jim...@ac...> - 2004-03-31 15:40:11
|
On 31-Mar-2004 Andre Berger wrote: > I see a strange behavior in noffle 1.1.5: articles Marked for > Download are never fetched. In the first place, I don't understand > why there are such articles anyway. Noffle fetches from upstream in basically two steps. First it issues an XOVER to get the overview info for the unread articles upstream. The filters run on the overview information. Articles are created at that point as 'Marked for download', assuming they survived filtering, and entered in the list of articles to be requested from upstream. The next step is to take articles to be requested in turn and download their bodies. If anything goes wrong with the second step, articles will be left as 'marked for download'. I see this quite often from my upstream; the upstream is usually overloaded and will have overviews available before bodies. The article bodies appear on subsequent fetches. If, however, your newsreader caches articles, you won't see the body when it arrives, as the newsreader will just show the 'body' it got before, the one saying 'Marked for download'. Which newsreader are you using? > I'm on modem dialup, and my > /etc/ppp/ip-up contains "noffle -n && noffle -f", my /etc/ppp/ip-down > "noffle -o". Ah. You're using online mode. That shouldn't make any difference, but I don't use it myself so I can't be sure. If you run noffle -f from the command line, it should give you some details on what it downloads. The same details will be recorded in the syslog 'news' as well. Check them over and see if you get many 'Retrieving failed' messages. -- Jim Hague - jim...@ac... Never trust a computer you can't lift. |
From: Andre B. <and...@we...> - 2004-04-09 06:59:01
|
* Jim Hague <jim...@ac...>, 2004-03-31 23:07 +0200: > On 31-Mar-2004 Andre Berger wrote: > > I see a strange behavior in noffle 1.1.5: articles Marked for > > Download are never fetched. In the first place, I don't understand > > why there are such articles anyway. > > Noffle fetches from upstream in basically two steps. First it issues an XOVER > to get the overview info for the unread articles upstream. The filters run on > the overview information. Articles are created at that point as 'Marked for > download', assuming they survived filtering, and entered in the list of > articles to be requested from upstream. > > The next step is to take articles to be requested in turn and download their > bodies. > > If anything goes wrong with the second step, articles will be left as 'marked > for download'. I see this quite often from my upstream; the upstream is usually > overloaded and will have overviews available before bodies. The article bodies > appear on subsequent fetches. If, however, your newsreader caches articles, you > won't see the body when it arrives, as the newsreader will just show the 'body' > it got before, the one saying 'Marked for download'. Which newsreader are you > using? > > > I'm on modem dialup, and my > > /etc/ppp/ip-up contains "noffle -n && noffle -f", my /etc/ppp/ip-down > > "noffle -o". > > Ah. You're using online mode. That shouldn't make any difference, but I don't > use it myself so I can't be sure. > > If you run noffle -f from the command line, it should give you some details on > what it downloads. The same details will be recorded in the syslog 'news' as > well. Check them over and see if you get many 'Retrieving failed' messages. Took me a while to figure out what went wrong: It was a timing problem. My news user agent sometimes fetched the articles between step one and step two, then listed them as fetched and subsequently ignored the bodies that arrived later. I made sure it won't run while a noffle fetch is in progress, and everything is OK now. Also, I switched to offline mode just in case. Thanks! -Andre |
From: Jim H. <jim...@ac...> - 2004-04-12 16:56:02
|
On 08-Apr-2004 Andre Berger wrote: > Took me a while to figure out what went wrong: It was a timing > problem. My news user agent sometimes fetched the articles between > step one and step two, then listed them as fetched and subsequently > ignored the bodies that arrived later. I made sure it won't run while > a noffle fetch is in progress, and everything is OK now. That makes it sound like your user agent is caching articles. Does it have any way of turning off article caching? There are some notes in docs/NOTES on various agents. -- Jim Hague - jim...@ac... Never trust a computer you can't lift. |
From: Dan J. <ji...@ji...> - 2004-06-21 20:09:59
|
Gentlemen, I remove the line from the requested/* file in question, but the article in question is often fetched anyway. Blast, there's no sure way to cancel a request once one has seen the ominous "[ NOFFLE INFO: Marked for download ]" $ set /var/spool/noffle/requested/news.gmane.org $ cat $1 <so...@ob...n't.want.to.download> $ ed $1 d wq $ noffle -f #often gets it anyway |
From: Dan J. <ji...@ji...> - 2004-08-31 18:10:05
|
Gentlemen, I clearly remove the unwanted requests, see: # ed /var/spool/noffle/requested/news.individual.net 131 ,d wq 0 but half an hour later, there they are back in that file, even though I long ago stopped browsing that group. Something is making real sure those requests stay in that file. I have to delete them twice before I connect to make sure I don't slurp them down. |