Hello
i thought i had sent this here already to bts. Turn out i missed it.
So here it goes.
Thilo Six schrieb/wrote:
>
> just a short addition, see below
>
May i ask then what is a real world use case for the unlimit builtin then?
(Just to make it clear, i am not ironic here, just
Hello Daniel,
Daniel Shahaf schrieb/wrote:
>> Now if unlimit would instead evaluate the maximum physical possible size for
>> that limit and activate that, i would say nice.
>
> Managing system resources is the OS's job, not zsh's. I suggest you
> look into configuring your OS to set the hard
Thilo Six wrote on Sat, Jan 02, 2016 at 20:28:39 +0100:
> I do argue (and that is what has caused this bug) that setting a limit that
> far
> beyond anything capable on this current system that it is not even technical
> able to handle that size of such a limit is useful.
> And that is just what
Control: retitle -1 zshbuiltins: Clarify the meaning of "hard limit" in the
documentation of 'unlimit'
Control: severity -1 wishlist
Thilo Six wrote on Thu, Dec 31, 2015 at 12:19:19 +0100:
> Daniel Shahaf schrieb/wrote:
> > Thilo Six wrote on Wed, Dec 30, 2015 at 17:12:17 +0100:
> >> So as i
Hello Daniel,
Daniel Shahaf schrieb/wrote:
>> May i ask then what is a real world use case for the unlimit builtin then?
>> (Just to make it clear, i am not ironic here, just interested trying to
>> understand it.)
>
> You might as well ask what's the purpose of having separate soft and
> hard
Daniel Shahaf schrieb/wrote:
> Thilo Six wrote on Wed, Dec 30, 2015 at 17:12:17 +0100:
>> The manpage says (as mentioned earlier):
>> unlimit [ -hs ] resource ...
>> The resource limit for each resource is set to the hard
>> limit.
>>
>> Again "hard limit" by its own is as
Thilo Six schrieb/wrote:
-- --
>> $ ulimit -v -m
>> virtual memory (kbytes, -v) unlimited
>> max memory size (kbytes, -m) unlimited
>>
>> I'm sure even with swap, there's no unlimited virtual memory available
>> on my machine.
>
>
> That is my main point. I think the "real
Thilo Six wrote on Wed, Dec 30, 2015 at 17:12:17 +0100:
> The manpage says (as mentioned earlier):
> unlimit [ -hs ] resource ...
> The resource limit for each resource is set to the hard limit.
>
> Again "hard limit" by its own is as ambiguous as "unlimited".
>
The
Hi Thilo,
Thilo Six wrote:
> in https://bugs.debian.org/807836 it was discovered that the Zsh builtin
> "unlimit" has potential unforeseen side-effects.
>
> An easy to reproduce case for the problem is documented in
> https://bugs.debian.org/807836#30
That example is IMHO a wrong usage of awk
Hello Axel,
Axel Beckert schrieb/wrote:
>> in https://bugs.debian.org/807836 it was discovered that the Zsh builtin
>> "unlimit" has potential unforeseen side-effects.
>>
>> An easy to reproduce case for the problem is documented in
>> https://bugs.debian.org/807836#30
>
> That example is IMHO
Hello Zsh maintainers,
in https://bugs.debian.org/807836 it was discovered that the Zsh builtin
"unlimit" has potential unforeseen side-effects.
An easy to reproduce case for the problem is documented in
https://bugs.debian.org/807836#30
The problem here is that unlimit sets the maximum input
11 matches
Mail list logo
