Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug#765410: ulimit broken as root if it fails once [origin: goswin-v-b@xxxxxx]

X-seq: zsh-workers 33472
From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: Bug#765410: ulimit broken as root if it fails once [origin: goswin-v-b@xxxxxx]
Date: Thu, 16 Oct 2014 09:22:26 +0100
Cc: 765410@xxxxxxxxxxxxxxx
In-reply-to: <141015194913.ZM13190@torch.brasslantern.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Organization: Samsung Cambridge Solution Centre
References: <20141015223329.GV5405@sym.noone.org> <141015194913.ZM13190@torch.brasslantern.com>

On Wed, 15 Oct 2014 19:49:13 -0700
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> This could also be fixed by having bin_ulimit read back the actual limit
> after a failure to set the hard limit and store that instead of keeping
> the "desired" hard limit around and trying to change it again.

I think that would be preferable --- I noted after the last ulimit query
(zsh-workers/33363, about a different implementation oddity) that this
looked potentially confusing.

pws

Follow-Ups:
- Re: Bug#765410: ulimit broken as root if it fails once [origin: goswin-v-b@xxxxxx]
  - From: Bart Schaefer

References:
- Fwd: Bug#765410: ulimit broken as root if it fails once [origin: goswin-v-b@xxxxxx]
  - From: Axel Beckert
- Re: Fwd: Bug#765410: ulimit broken as root if it fails once [origin: goswin-v-b@xxxxxx]
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author