Problems with dead backends and Gnus dying

Problems with dead backends and Gnus dying

[Jack Vinson]

Hello,

My main comment here is that Gnus is behaving "badly" when a backend dies
on it.  I am having trouble with the nntp and nnslashdot backends, but I
would still like to read from nnml and other backends when they are
working.  nnSlashdot, in particular, is giving me an error and somehow not
respecting the unwind-protect.  As a result, if I get an error when Gnus
loads, then I cannot read anything.  Bummer.  

My nntp news service was recently having many problems.  I don't
know what was going on, but Gnus would just sit there FOR HOURS, trying to
connect to the nntp server.  Eventually it would come back with a "server
seems to not be responding, continue?" question.  But why should this take
so long?  Is there some timeout setting we can give Gnus for reaching
backends?

I am also having the problem with Slashdot that someone else was having.
The error is during an attempt to use match-string within the forms sent to
mm-with-unibyte-buffer.  I can send the full backtrace if someone is really
interested.

Any ideas?

-- 
JackVinson@Yahoo.com
Bart: I will not teach others to fly.

Re: Problems with dead backends and Gnus dying

[Lars Magne Ingebrigtsen]

Jack Vinson <JackVinson@yahoo.com> writes:

> My main comment here is that Gnus is behaving "badly" when a backend dies
> on it.  I am having trouble with the nntp and nnslashdot backends, but I
> would still like to read from nnml and other backends when they are
> working.  nnSlashdot, in particular, is giving me an error and somehow not
> respecting the unwind-protect.  As a result, if I get an error when Gnus
> loads, then I cannot read anything.  Bummer.  

`(setq debug-on-error t)', repeat the bug and mail me the resulting
backtrace.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen