All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich.Strelow@schering.de
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] make dep not working on HP-UX
Date: Fri, 25 Jun 1999 17:55:04 +0200	[thread overview]
Message-ID: <C125679B.00577445.00@BE2314.schering.de> (raw)



I have had a similar problem on our production HP-UX systems. Running ls *
on a directory with a lot of files gives
ksh: /usr/bin/ls: arg list too long

To solve this problem you need to set the HP-UX kernel parameter
large_ncargs_enabled  1
and rebuild the HP-UX kernel.

Here is the information from HP Electronic Support Center:

Problem Description

What is the impact of changing the kernel parameter
"large_ncargs_enabled" from 0 to 1?

What is the meaning of this parameter?

Configuration Info

Operating System - HPUX
Version-
Hardware System - HP 9000
Series -

Solution
When large_ncargs_enabled is set to "1", it increases the default
"environment size" (the memory set aside to be your login
environment - to hold your PATH variable, etc.) from 20478 to
2048000. SAM doesn't have any info about this parm or any max/minvalue.

If you have been having trouble using an "rm *" on really big
directories (it was running out of environment space), the command
will work when you set it to 1.  Regarding system performance, it
will eat up extra memory (2 M vs. 20 K), but if you don't have too
many users and you have plenty of RAM, it shouldn't be a problem.

Ulrich
---------------------------------------------
Ulrich Strelow
<ulrich.strelow@schering.de or
ulrich_strelow@yahoo.com>
Berlin, Germany

             reply	other threads:[~1999-06-25 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-25 15:55 Ulrich.Strelow [this message]
1999-06-25 18:29 ` [parisc-linux] make dep not working on HP-UX John David Anglin

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=C125679B.00577445.00@BE2314.schering.de \
    --to=ulrich.strelow@schering.de \
    --cc=parisc-linux@thepuffingroup.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.