Re: slrn broke after power failure

Path	csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod
From	songbird <songbird@anthive.com>
Newsgroups	linux.debian.user
Subject	Re: slrn broke after power failure
Date	Tue, 19 Apr 2022 17:10:01 +0200
Message-ID	<EdXEl-9O2R-13@gated-at.bofh.it> (permalink)
References	<EdFHr-9CSV-11@gated-at.bofh.it> <EdW5z-9N1w-3@gated-at.bofh.it>
X-Mailbox-Line	From debian-user-request@lists.debian.org Tue Apr 19 15:08:52 2022
Old-Return-Path	<gldu-debian-user-2@m.gmane-mx.org>
X-Amavis-Spam-Status	No, score=-6.662 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate:hard: -4.6
X-Injected-Via-Gmane	http://gmane.org/
Organization	the little wild kingdom
Reply-To	songbird <songbird@anthive.com>
User-Agent	slrn/1.0.3 (Linux)
X-Mailing-List	<debian-user@lists.debian.org> archive/latest/788223
List-ID	<debian-user.lists.debian.org>
List-URL	<https://lists.debian.org/debian-user/>
List-Archive	https://lists.debian.org/msgid-search/29v2ji-in6.ln1@anthive.com
Approved	robomod@news.nic.it
Lines	46
Sender	robomod@news.nic.it
X-Original-Date	Tue, 19 Apr 2022 10:58:10 -0400
X-Original-Message-ID	<29v2ji-in6.ln1@anthive.com>
X-Original-References	<547a28c4-b359-539d-ee38-9371c1419a20@surfnaked.ca> <slrnt5te7k.4oq.curty@einstein.electron.org>
Xref	csiph.com linux.debian.user:247357

Show key headers only | View raw

Curt wrote:
> On 2022-04-18, Charlie Gibbs <cgibbs@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

Thread

Re: slrn broke after power failure Charlie Gibbs <cgibbs@surfnaked.ca> - 2022-04-18 22:00 +0200
  Re: slrn broke after power failure Curt <curty@free.fr> - 2022-04-19 15:30 +0200
    Re: slrn broke after power failure songbird <songbird@anthive.com> - 2022-04-19 17:10 +0200
  Re: slrn broke after power failure Tim Woodall <debianuser@woodall.me.uk> - 2022-04-19 18:10 +0200
    Re: slrn broke after power failure Tim Woodall <debianuser@woodall.me.uk> - 2022-04-19 18:20 +0200

csiph-web