Curt wrote: > On 2022-04-18, Charlie Gibbs <cgi...@surfnaked.ca> wrote: >> >> Again, my issue is not with the spool, but why slrn seems to >> be trying to bypass it and access the server directly. Unless >> that "server read failed" message is a red herring... >> > > > > slrn --debug FILE > > Then look in FILE for possible edification.
yes, also i've been trying to get through the source code and see what it might give any clues. art.c is the only file that has that specific error message. unfortunately i don't have time to dig into this for a while. :( here are suggestions to try: subscribe to a new group and then download 100 articles and then use find to list all the changed files and directories (to see what is being touched by slrn). after that go in and make one of those files zero length to see if that replicates the error message when you try to go look at that again. then remove the zero length file and remove the .overview file for that group and see if you can then get that message again. i think a missing .overview file should be regenerated every time there is a new article downloaded. these are guesses. don't do this for a group you really have a lot of articles in already if you don't want to lose them. i regularly clean out old articles in my spool when it gets too full and that automatically regenerates the .overview files but it is leafnode that does that for me and not slrn. so i'm doing things differently, but it should all still work about the same way in the end. songbird
