[lfs-dev] Restrict the scope of the ulimit -s 32768

Daniel Schepler dschepler at gmail.com
Sun Jun 7 13:02:30 PDT 2015


On Sun, Jun 7, 2015 at 12:46 PM, Bruce Dubbs <bruce.dubbs at gmail.com> wrote:

> Daniel Schepler wrote:
>
>> This patch is against the systemd branch (though hopefully there shouldn't
>> be any problems applying to trunk either).  I didn't run into any new
>> failures in subsequent builds; though for some reason, I'm getting this
>> test suite failure in make (putting ulimit -s 32768 on it doesn't help,
>> though):
>>
>> misc/fopen-fail .........................................
>> Test timed out after 5 seconds
>> Error running /sources/make-4.1/tests/../make (expected 512; got 14):
>> /sources/make-4.1/tests/../make -f work/misc/fopen-fail.mk
>>
>> Caught signal 14!
>> FAILED (0/1 passed)
>>
>
> I don't know why you feel the need to restrict the ulimit change to only
> one process.  We do that in chroot and as soon as you leave chroot, that
> limit is no longer effective.  It's not like the change is permanent for
> arbitrary commands forever.


It just seems a little sloppy to let the ulimit increase continue to have
effect throughout the rest of the book until rebooting into the system,
when it's only needed for this one thing.  It was just a suggestion, though.
-- 
Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/lfs-dev/attachments/20150607/bab99ea6/attachment.html>


More information about the lfs-dev mailing list