Re: some problems with chpst again
Gerrit Pape <[email protected]>
| Newsgroups | gmane.comp.misc.pape.general |
|---|---|
| Message-ID | <20040511170152.23180.qmail@29e469d711f2e9.315fe32.mid.smarden.org> |
On Tue, May 11, 2004 at 04:40:55PM +0000, Payal Rathod wrote: > On Tue, May 11, 2004 at 02:50:50PM +0000, Gerrit Pape wrote: > > Yes, softlimit -a is different from chpst -m. softlimit -m would be the > > So what switch do I use for chpst? To have chpst doing the same as `softlimit -a`, you need call it with the name softlimit: # ln -s chpst /usr/local/bin/softlimit # /usr/local/bin/softlimit -a ... > > same. Payal, what does > > $ chpst -vm3000000 true > > say on your system? Some operating systems do not support -a. > > I have > # chpst -vm3000000 true > # echo $? > 0 Ok, so your system does support RLIMIT_VMEM or RLIMIT_AS, I was afraid your `softlimit -a` was a no-op. chpst -m x does the same as softlimit -m x (same as -d x -s x -l x -a x). So one of -d, -s, -l, causes the problem for you. Regards, Gerrit.