Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Agent weirdness
Date: Tue, 14 Jan 2004 00:04:55 +0100	[thread overview]
Message-ID: <plop87isjgz5j8.fsf@gnu-rox.org> (raw)
In-Reply-To: <uzncssh0v.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Mon, 12 Jan 2004 21:45:36 -0500")

[-- Attachment #1: Type: text/plain, Size: 4327 bytes --]

On 13 Jan 2004, Kevin Greiner<kgreiner@xpediantsolutions.com>
verbalized:

 <snip>

> 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 !!

Here is the log of a session supposed not to be plugged, with nntp
backend agentized:

,----
| --- SIGALRM (Alarm clock) @ 0 (0) ---
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
| connect(6, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.0.0.1")}, 28) = -1 ENETUNREACH (Network is unreachable)
| --- SIGIO (I/O possible) @ 0 (0) ---
| --- SIGIO (I/O possible) @ 0 (0) ---
| --- SIGIO (I/O possible) @ 0 (0) ---
`----

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.

Regards,

zeDek

P.S: sorry for long lines
-- 
Xavier Maillard
http://www.gnu-rox.org/~zedek/cgi-bin/wiki.pl


[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2004-01-13 23:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 21:38 [Pb]: Denied access when unplugged ? Xavier Maillard
2004-01-13  0:13 ` Agent weirdness (was: [Pb]: Denied access when unplugged ?) Xavier Maillard
2004-01-13  2:45   ` Agent weirdness Kevin Greiner
2004-01-13  5:31     ` Xavier Maillard
2004-01-13 23:04     ` Xavier Maillard [this message]
2004-01-14  1:09       ` Kevin Greiner
2004-01-13  0:18 ` [Pb]: Denied access when unplugged ? Kevin Greiner
2004-01-13  0:42   ` Xavier Maillard
2004-01-13  0:46   ` Xavier Maillard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=plop87isjgz5j8.fsf@gnu-rox.org \
    --to=zedek@gnu-rox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).