From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: file descriptor usage?
Date: 22 Mar 1997 15:33:21 +0100 [thread overview]
Message-ID: <m2iv2kvvwu.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Scott Blachowicz's message of Fri, 21 Mar 1997 16:49:27 -0800
Scott Blachowicz <scott@bloke.statsci.com> writes:
> Our news server has finally been reconstructed and I'm playing with
> later versions of gnus and started getting wierd problems with emacs
> failing to load various files, my visiting a file only to get an
> error about the file exists, but is unreadable and such. All of the
> weirdness happened after I did `M-x gnus' (triggering the autoload
> of stuff). Finally I saw an error message that led me to check my
> 'limit' command in my shell and sure enough, it said that I had a
> limit of 64 file descriptors. I bumped it up to 256 and now I can
> run gnus.
What was the exact error message?
> So, my question is...has something happened that that would cause
> gnus/emacs (19.33 & xemacs 19.14) to chew up a whole lot more file
> descriptors? Like I said, it's been a while...this might be the
> first time that I've gotten any 5.4.x release going...
Gnus is now a gazillion small files instead of one biiig file, and I
guess it might be possible that the chain of `require's and
`autoload's would keep a big number of files open at once (while
loading).
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-03-22 14:33 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 [this message]
1997-03-22 18:34 ` Sudish Joseph
1997-03-25 18:09 ` Scott Blachowicz
1997-03-30 8:49 ` Lars Magne Ingebrigtsen
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=m2iv2kvvwu.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).