Roland Mainz <[EMAIL PROTECTED]> wrote:
> > Exactly how is ulimit -T portable didn't you already say it *does not*
> > exist as part of POSIX and isn't available on other systems ?
>
> I've listed two other operating systems (AIX+IRIX) who already have this
> kind of functionality (unfortunately with two slightly different names
> (|RLIMIT_PTHREADS| vs. |RLIMIT_THREADS|)).
The existence of such functions on other OS does not verify that they have been
defined in a sane way. Linux e.g. also defines RLIMIT_MEMLOCK and the way it
has
been implemented, it makes rightful/privileged calls to
mlockall(MCL_CURRENT|MCL_FUTURE) not working as expected.....
The ulimit(1) POSIX documentation _only_ mentions "-f file bloks". All other
functionality is beyond the ulimit(2) call.
Given the fact that even the current set of ksh93 ulimit(1) options is beyond
the {get!set}rlimit() set, I see no reason to require new functinality to be
implemented using {get!set}rlimit().
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
