From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/56008 Path: main.gmane.org!not-for-mail From: Kevin Greiner Newsgroups: gmane.emacs.gnus.general Subject: Re: Agent weirdness Date: Tue, 13 Jan 2004 20:09:42 -0500 Sender: ding-owner@lists.math.uh.edu Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1074042694 13023 80.91.224.253 (14 Jan 2004 01:11:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 14 Jan 2004 01:11:34 +0000 (UTC) Original-X-From: ding-owner+M4548@lists.math.uh.edu Wed Jan 14 02:11:31 2004 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AgZZD-0004Av-00 for ; Wed, 14 Jan 2004 02:11:31 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1AgZYk-0005QL-00; Tue, 13 Jan 2004 19:11:02 -0600 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1AgZYb-0005QD-00 for ding@lists.math.uh.edu; Tue, 13 Jan 2004 19:10:53 -0600 Original-Received: from quimby.gnus.org (quimby.gnus.org [80.91.224.244]) by justine.libertine.org (Postfix) with ESMTP id BFCBF3A0033 for ; Tue, 13 Jan 2004 19:10:51 -0600 (CST) Original-Received: from news by quimby.gnus.org with local (Exim 3.35 #1 (Debian)) id 1AgZYZ-000484-00 for ; Wed, 14 Jan 2004 02:10:51 +0100 Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-Lines: 98 Original-NNTP-Posting-Host: rrcs-midsouth-24-172-86-250.biz.rr.com Original-X-Trace: quimby.gnus.org 1074042651 15875 24.172.86.250 (14 Jan 2004 01:10:51 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: Wed, 14 Jan 2004 01:10:51 +0000 (UTC) User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) Cancel-Lock: sha1:XE+JMyMiTxIuWMAbrXMc8a7tH+k= Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:56008 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:56008 Xavier Maillard writes: > On 13 Jan 2004, Kevin Greiner > verbalized: > > > >> OK, let's start with what version of gnus are you running? >> >>> Ok I did investigations and here is something I saw. Whenever I have >>> a network connection (ie I have my eth0 up), I can enter into an >>> agentized group (with agentized/cached articles). If a group doesn't >>> have any agentized article it fails which sounds good to me. >> >> Are you running plugged, or unplugged, during this test. >> >>> Now the weirdness, If for a reason or another, I switch off the >>> network connection, Gnus: >>> >>> * fails to start correctly arguing it can't open nntp '.' >>> (news.nerim.net) >>> * if I continue, and try to enter a group containing agentized >>> articles, it fails too >>> >>> Giving the fact that when in train I don't have any network >>> connection, I won't be able to read agentized newsgroups. >> >> Try using (gnus-unplugged) to start gnus. > > I tried many times without success. Whenever my network connection > disappear, Gnus complains. I have launched a ntrace on gnus to see what > is going on. What I 've seen is funny ! > > Even explicitly telling Gnus not to go plugged, it tries to connect to > my nntp server !! Now that's the behavior that I was tring to fix with the last update to gnus-open-server. > Here is the log of a session supposed not to be plugged, with nntp > backend agentized: np, I believe you. > > As you surely see, Gnus (or Emacs) is attempting to connect whereas my > current configuration doesn't say so: > > ,---- > | (message "##### Not yet in agentized mode") > | (setq gnus-select-method '(nntp "news.nerim.net")) > | (setq gnus-server-unopen-status 'offline) > | (setq gnus-plugged nil) > | ;;(setq gnus-agent t) > | (message "Fin du chargement...") > `---- > > Note that the configuration above is my default and has *always* worked > this way except for the `gnus-server-unopen-status` variable which was > 'nil'. > >>> Is this the default behaviour ? I suppose it is not but it acts this >>> way here. >>> >>> AFAIK, I followed Gnus manual part on Agent and just checked I did >>> things correctly so... >>> >>> I really need help with that :) >>> >>> Why does Gnus complain it can't open news.nerim.net when it is >>> supposed to be _unplugged_ ?? >> >> Being plugged, or unplugged, has very little to do with the >> availability of a network connection. > > Hmm, my opinion on that is that gnus-open-server function doesn't > work for me at that time. Dunno if it is related to the latest patch you > talked about before but what is sure is that with Gnus 5.10.1 version > all worked like a charm here :) > > I am about to give up since I don't have more time to spend on this. I > will try to 'rollback' that patch (applied against 5.10.3) and see how > all is going on. Just to let you know, prior to 5.10.3, gnus always tried to open the server. The plugged/unplugged status and gnus-server-unopen-status simply controlled how it handled the connection failure. If you have any time left for this, I appreciate your debugging gnus-open-server. Eval the function then execute (debug-on-entry 'gnus-open-server) before starting gnus. The only function that you may need to step into is gnus-get-function. If you are unplugged and the gnus-command-method names an agentized server, gnus-get-function should return nnagent-open-server. If it returns nntp-open-server then the bug is in gnus-open-server (that's why you may need to step into it). Kevin