* Roland McGrath ([EMAIL PROTECTED]) wrote: > > Two questions: 1) This changes the interface for consumers of > > /proc/[pid]/status data, do we care? Adding new line like this should be > > safe enough. > > As far as I can tell, noone fretted about the addition of Threads:, > ShdPnd:, etc., which were not always there.
Sounds good ;-) > > 2) Perhaps we should do /proc/[pid]/rlimit/ type dir for each value? > > This has been asked for before. > > Is the request to see the limit settings, or the current usage, or both? > What kind of format are you suggesting? I don't see a need for something > with a million little files. Also, for some of the limits the correct > current usage count is not trivial to ascertain. (And for others like > RLIMIT_FSIZE and RLIMIT_CORE, it is of course not meaningful at all.) Probably just one file per rlimit with usage, cur, max. thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
