From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: file descriptor usage?
Date: 30 Mar 1997 10:49:48 +0200 [thread overview]
Message-ID: <m2encxzrv7.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Scott Blachowicz's message of Tue, 25 Mar 1997 10:09:05 -0800
Scott Blachowicz <scott@bloke.statsci.com> writes:
> I think I might have the nocem stuff enabled...would it be doing a
> bazillion separate connections for THAT?
No, it's an, uhm, feature of how virtual servers are handled. For
some reason, Gnus believes that you have several (similar) virtual
servers, so you get these results. I have yet to come up with a fix.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1997-03-30 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-22 0:49 Scott Blachowicz
1997-03-22 14:33 ` Lars Magne Ingebrigtsen
1997-03-22 18:34 ` Sudish Joseph
1997-03-25 18:09 ` Scott Blachowicz
1997-03-30 8:49 ` Lars Magne Ingebrigtsen [this message]
1997-03-30 21:57 ` David Moore
1997-03-31 10:36 ` Lars Magne Ingebrigtsen
1997-03-30 23:41 ` Scott Blachowicz
1997-03-30 23:58 ` Scott Blachowicz
1997-03-31 0:38 ` David Moore
1997-03-31 17:10 ` Scott Blachowicz
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=m2encxzrv7.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@gnus.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).