* Jim B said: > On Tue, 11 Jan 2000, Marek Habersack wrote: > > > He can't, true. But shell-based limits aren't particularily good way of > > setting > > limits. They are by definition bound to one kind of shell - csh or bash or > > whatever. In case you, or the user, decideds to change his shell, you loose > > all the limits. PAM and/or shadow utilities (or lshell) are much better. > > Correct. But this is the crux of this whole thread. I don't see any way, > *other than* shell limits, of setting max Virtual Memory usage. The other > resources yes, VMem no.... And the pam_limits 'as' + 'rss' + 'data' + 'memlock' + 'stack' parameters? They all give you fine-grained control over the user's memory.
marek
pgpkS8gsSzPfY.pgp
Description: PGP signature
