Re: Suggest documentation of "soft limit" logic for chpst

[Jared Rhine <jared@wordzoo.com>]

On Tue, 2005-11-22 at 05:54 +0100, Laurent Bercot wrote:
> > I had been trying to raise the limit on number of open files via 'chpst
> > -o 10000'.  I thought this was working properly, so I was focused on
> > examining the daemon for bugs.  Then I finally had the insight to test
> > whether 'chpst -o 10000 && ulimit -a' was doing what I expect.  Now I'm
> > doing a 'ulimit -n 10000' instead of a 'chpst -o 10000'.
> 
> chpst is not a shell builtin, and does not work the way ulimit does.

Sorry.  A typo of mine caused you to overinterpret my cluelessness.  I
am aware of both ulimit and chpst's behavior; I could not be using chpst
successfully in other contexts without that awareness.

The actual command I used to test was `chpst -o 10000 sh -c 'ulimit
-a'`.

The rest of my concerns still stand.  It would be helpful to have the
specific soft/hard behaviors of chpst documented in the man page.  chpst
may still benefit from fuller ulimit-style support (specifically
raising), as opposed to only the "limit" operation of setrlimit(2).  As
I believe both chpst and the shell ulimit call use the same system call
to change process limits, chpst could in theory be made to support more
ulimit-style features.

> By the way, 10000 is overkill.

With respect, since I did not indicate the context or appliciation for
my need for 10K open files, you don't have any basis by which to judge
whether it's overkill.  Trust me, I need 10K open files for the
application in question, and there is nothing amiss with my application,
system, or design.

I appreciate your attempts at education.

-- 
Jared Rhine <jared@wordzoo.com>