From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/1909 Path: news.gmane.org!not-for-mail From: Kevin Greiner Newsgroups: gmane.emacs.gnus.user Subject: Re: bug? gnus unreliable for sympatico.ca news server Date: Mon, 20 Jan 2003 00:44:57 -0600 Message-ID: References: <3E247A9E.7060302@yahoo.com> <3E25B7B6.20602@yahoo.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668532 13151 80.91.229.2 (31 Jan 2006 00:48:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:48:52 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:29:53 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 216.12.206.169 Original-X-Trace: quimby.gnus.org 1043045683 5799 216.12.206.169 (20 Jan 2003 06:54:43 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 20 Jan 2003 06:54:43 GMT User-Agent: Gnus/5.090013 (Oort Gnus v0.13) Emacs/21.2 (i386-msvc-nt5.1.2600) Cancel-Lock: sha1:KFoZe+/dQjQmJr83VK/WGbGo3v4= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2049 Original-Lines: 45 X-Gnus-Article-Number: 2049 Tue Jan 17 17:29:53 2006 Xref: news.gmane.org gmane.emacs.gnus.user:1909 Archived-At: * Tong * writes: > Thanks for such a quick respond. > > Kevin Greiner wrote: >>>The latest version of Oort gnus should fix this problem. As I added a >>>timer to break out of hangs by closing the current connection then >>>opening a new connection and re-issuing the current command. > > latest version of Oort gnus has already a workaround for my problem? > Great news. > >>>I'll look into added the GROUP command right before every ARTICLE as >>>that would help avoid unnecessary connection teardown and rebuild. > > Great! > >> Sorry forgot the most important part. The new code does a better job >> of recovering from sockets closed by the NNTP server. However, it can >> hang if the server chooses to simply ignore a connection (I have one >> server that closes idle connections while another ignores them on the >> theory that they've hung a resource-hungry client). To avoid the >> hang, you need to customize nntp-connection-timeout. The value is in >> seconds. I've used 30 to good effect for a couple of months now. >> For what you are describing, you probably won't need >> nntp-connection-timeout. Still it's there if you need it. > > Does it 'nntp-connection-timeout' correspond to the timer you just > mentioned, to break out of hangs? Yes. > Then I guess I need it, 'cause seems to me sympatico.ca news server > just ignore my (postponded) ARTICLE request, and hang my telnet > session. All other commands, like xover, list, etc, will get a respond > very fast, even after idle for a long time... Hope new gnus version > can handle situations like this. (A group command should be > enough. :-> ) Let me how this works out for you. I use three different servers and all three have different behaviors when a connection is idled. I'd like to use a general purpose solution but sympatico may fall outside of the solution as it is currently written. Kevin