Thilo Six schrieb/wrote: -- <snip> -- >> $ 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 problem" here is the definition of a > "hard limit". My definition of a "hard limit" is either the maximum physical > capability of the hardware being used, or a subset of that when a admin sets a > hard limit via e.g. /etc/security/limits.conf . > ...and not some random value without any meaning.
I thought it would be helpful to be more wordy about what i mean. unlimited by its own is ambiguous. unlimited can mean ∞ but IMHO an other valid meaning of unlimited is: "as much, as there is without restrictions" And that is what i am talking about. 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". So as i said above, the definition of "hard limit" should be explicit in the man page, e.g.: The resource limit for each resource is set to the hard limit, that is ... I want to add, i do not force Zsh maintainers to choose either of the meanings again i just ask Zsh maintainers kindly to clearly document which one they have choosen. I hope my point which lead to this bug is now more easier to follow. kind regards, Thilo