Robert Elz wrote, on 09 Nov 2020: > > Date: Mon, 9 Nov 2020 10:38:26 +0000 > From: "Austin Group Bug Tracker via austin-group-l at The Open > Group" <[email protected]> > Message-ID: <[email protected]> > > | I have realised the desired action doesn't cover the behaviour when more > | than one resource-selection option is specified. If no operand is present, > | both ksh and bash report the limits for the selected options using the > same > | format as for -a. > > as does bosh and zsh. Other shells simply report the last one requested > (ash derived shells, incl dash, plus yash, mksh and old pd ksh - so my guess > would be ksh88 as well but I don't have that to test).
I tested ksh88 and ksh93 but just said "ksh" as I didn't need to be specific about the version. > | The following is a revised proposal that specifies the case when no > operand > | is present > > This one has two problems - first it specifies things that many > shells do not do, which is probably not a good idea, The ksh and bash behaviour of reporting multiple values seems more useful to me, but I wouldn't object if others want to make this unspecified. It's also worth bearing in mind that ulimit is part of the XSI option (i.e. required for UNIX conformance, but not for POSIX conformance), and the ksh and bash behaviour is what all certified UNIX systems do. > and second > the way it is written makes it seem that something should be done > with > ulimit -S -a 1234 No it doesn't. The SYNOPSIS line in which -a appears is just: ulimit [-H|-S] -a -- Geoff Clare <[email protected]> The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
