zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ifh.de>
To: Anthony Heading <aheading@jpmorgan.com>,
	zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: Bizarre Solaris problem
Date: Fri, 14 Nov 1997 15:15:05 +0100	[thread overview]
Message-ID: <199711141415.PAA22498@hydra.ifh.de> (raw)
In-Reply-To: "Anthony Heading"'s message of "Thu, 13 Nov 1997 17:17:15 MET." <199711131717.RAA04184@gmp-etpres1.uk.jpmorgan.com>

Anthony Heading wrote:
> Haha!  A quick update in case anyone is thinking about this.
> 
> The problem I've just tracked down to process limits.  csh is
> initialising with the maxmimum number of file descriptors set to 64
> (indeed the value of OPEN_MAX and supposedly the maximum limit
> therefore for RLIMIT_NOFILE).
> 
> getrlimit(), however,  believes that the maximum number of file
> descriptors is 1024, and zsh is bumping the limit up to that value.
> This appears to confuse the 4.1.3 gethostbyname().

We saw this business apropos of something else a while ago.  OPEN_MAX
is actually not the maximum limit, since it's run-time configurable
under Solaris 2.  So presumably the difference that's causing the OS bug
to show up is because csh is too old-fashioned to care.  Unless there's
some reason for not following getrlimit() if all those descriptors aren't
needed.

-- 
Peter Stephenson <pws@ifh.de>       Tel: +49 33762 77366
WWW:  http://www.ifh.de/~pws/       Fax: +49 33762 77413
Deutsches Elektronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, Platanenallee 6, 15738 Zeuthen, Germany.


  parent reply	other threads:[~1997-11-14 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-12 13:22 Anthony Heading
1997-11-12 17:45 ` Bart Schaefer
1997-11-13 17:17   ` Anthony Heading
1997-11-13 18:55     ` Richard Coleman
1997-11-14 14:15     ` Peter Stephenson [this message]
1997-11-20 15:18       ` Anthony Heading

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=199711141415.PAA22498@hydra.ifh.de \
    --to=pws@ifh.de \
    --cc=aheading@jpmorgan.com \
    --cc=zsh-workers@math.gatech.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).