supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jared Rhine <jared@wordzoo.com>
Subject: Suggest documentation of "soft limit" logic for chpst
Date: Mon, 21 Nov 2005 12:46:19 -0800	[thread overview]
Message-ID: <4382321B.9050700@wordzoo.com> (raw)

It might be helpful to have a little bit of discussion on the chpst
manpage which outlines that chpst is dealing with soft limits.

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

I had read the manpage a couple of times while doing this investigation,
but it's brief with respect to what chpst is really doing with these
switches.  It wasn't until I saw "softlimit(8)" at the bottom that I
started to suspect the source of my problem.  Maybe mentioning the
actual logic in-line with the manpage text would be useful.

I'd also be in favor of chpst being able to raise limits (hard ulimit)
to emulate ulimit more directly, but that's a separate conversation.


             reply	other threads:[~2005-11-21 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 20:46 Jared Rhine [this message]
2005-11-22  4:54 ` Laurent Bercot
2005-11-23  5:47   ` Jared Rhine
2005-11-23 13:35     ` Laurent Bercot
2012-09-21  7:04 suggest " Gildas

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=4382321B.9050700@wordzoo.com \
    --to=jared@wordzoo.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 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).