On 2024-10-15, Christian Schulte <cs@schulte.it> wrote:
> On 10/15/24 12:09, Stuart Henderson wrote:
>> On 2024-10-15, Zé Loff <zeloff@zeloff.org> wrote:
>>> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
>>>> ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
>>>> ulimit -n `ulimit -aH | grep nofiles | awk '{print $2}'`
>>
>> ulimit -d `ulimit -dH` etc... but then there's no point setting a
>> separate hard limit in login.conf.
>
> Of course. I am the only user on that system and the only limits I want
> "my" xsession to be in effect on that system are the hard limits setup
> by the kernel.
Why, do you only run one program at a time? OpenBSD doesn't cope
amazingly well with over-allocating memory..Think of these limits as
protection against problems rather than as a restriction to stop you
doing things.
> I am reading that already. That thing should not swap. It does. Some
> application may well not have been that nice to the memory allocator.
See the dma_constraint stuff in particular.
> The Java VM seems to have this gotten right. Fingers crossed.
That's actually what I was specifically thinking of when I wrote this:
>> IIRC some things do use ulimit -d as a hint to how much memory they can
>> allocate.
- if datasize limits are too high I think you need to start fiddling
with -Xmx to stop it using too much.
--
Please keep replies on the mailing list.
No comments:
Post a Comment