Haiku-related ulimit overhaul:
• print ulimit -a with the flag, like most other shells do • move ulimit-1 regression test to ulimit-2 and exclude on Haiku: it can only set the -n and -V limits AFAICT • document that some OSes (here: Haiku) can only set the soft limits (so “ulimit -nS 1024” is okay but -S is required) • check “ulimit -c 0”, which dot.mkshrc uses, everywhere (if it errors out, hack around it or stub it out with MKSH_NO_LIMITS)
This commit is contained in:
4
funcs.c
4
funcs.c
@@ -38,7 +38,7 @@
|
||||
#endif
|
||||
#endif
|
||||
|
||||
__RCSID("$MirOS: src/bin/mksh/funcs.c,v 1.328 2017/03/17 22:45:50 tg Exp $");
|
||||
__RCSID("$MirOS: src/bin/mksh/funcs.c,v 1.329 2017/03/19 18:05:28 tg Exp $");
|
||||
|
||||
#if HAVE_KILLPG
|
||||
/*
|
||||
@@ -3655,7 +3655,7 @@ c_ulimit(const char **wp)
|
||||
if (!all)
|
||||
print_ulimit(rlimits[i], how);
|
||||
else for (i = 0; i < NELEM(rlimits); ++i) {
|
||||
shprintf("%-20s ", rlimits[i]->name);
|
||||
shprintf("-%c: %-20s ", rlimits[i]->optchar, rlimits[i]->name);
|
||||
print_ulimit(rlimits[i], how);
|
||||
}
|
||||
return (0);
|
||||
|
||||
Reference in New Issue
Block a user