Re: checking news problem

Robert Holtzman <[email protected]> wrote:
> I have the previously discussed problem of checking news taking 3-4
> minutes. The only fix I could find with a search engine was to delete
> and recreate the .jnewsrc file. Does that mean I have to use the
> --create option and resubscribe to the groups I want? That means I
> will get all previously read messages. I haven't seen any other fix
> nor have I seen anything addressing the cause.

There could be any number of reasons for "checking news" to take
several minutes.  For example, you could have a slow connection and
many newsgroups, or the server could be overloaded, or there could be
a network problem between you and the server, ...

Are you reading the active file upon startup?  That is, are you
starting up slrn with the -a option, or do you have 

  set read_active 1

in your .slrnrc file?  If not, then try enabling this option.

There should be no need to ever delete your newsrc file unless
testing.  But if you have deleted your newsrc file, then you will need
to use the --create option to create a new one.  But again, a delay in
startup is unlikely to be caused by your newsrc file.

> Just FYI the output of slrn --debug &HOME/slrn.debug was unintelligible
> to me.

The debug file is mainly a log of what is set to and from the server
and is useful to diagnosing problems associated with the underlying
NNTP protocol.

I hope this helps.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/