From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Agent weirdness
Date: Tue, 13 Jan 2004 06:31:10 +0100 [thread overview]
Message-ID: <plop87d69omn35.fsf@gnu-rox.org> (raw)
In-Reply-To: <uzncssh0v.fsf@xpediantsolutions.com>
[-- Attachment #1: Type: text/plain, Size: 3054 bytes --]
On 13 Jan 2004, Kevin Greiner<kgreiner@xpediantsolutions.com> said:
> Xavier Maillard <zedek@gnu-rox.org> writes:
<snip>
> OK, let's start with what version of gnus are you running?
Fresh CVS copy.
>> 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.
I have set in my .gnus: (setq gnus-plugged nil) so it should tell gnus
to be unplugged at startup.
>> 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 just did and the point is with eth0 up, there is no problem for me
but if shut the network connection and launch gnus with
'gnus-unplugged', it complains at startup not to be able to open "nntp
blah blah blah, Do you want to continue (y or n) ?". If I say y, then
the server is marked as 'denied' in the server buffer (which is normal).
>>
>> 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.
> If I am plugged but have no network connection, gnus will fail while
> attempting to open a connection. This will result in the server being
> marked in accordance with gnus-server-unopen-status (by the way, what
> do you have this set to?). Depending upon gnus-server-unopen-status,
> the server may be marked as either denied, offline, or you may be
> prompted as to what to do.
Here it is:
,----[ C-h v gnus-server-unopen-status RET ]
| gnus-server-unopen-status's value is nil
|
| The default status if the server is not able to open.
| If the server is covered by Gnus agent, the possible values are
| `denied', set the server denied; `offline', set the server offline;
| nil, ask user. If the server is not covered by Gnus agent, set the
| server denied.
|
| You can customize this variable.
|
| Defined in `gnus-int'.
|
| [back]
`----
> If I am unplugged but have a network connection, gnus will immediately
> mark all agentized servers as being offline while unagentized servers
> will be marked as denied.
Which is the normal behavior I should expect here too :)
zeDek
--
"GNU is my religion"
.O. Xavier Maillard
..O Reims - France
OOO +33 6 62 59 68 62
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-01-13 5:31 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 [this message]
2004-01-13 23:04 ` Xavier Maillard
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=plop87d69omn35.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).