On Fri, Aug 10, 2012 at 23:35, Friedrich Locke wrote:
> There are different level of responsaiblity.
>
> 0. setrlimit should be allowed to set any limit the super user wants.
> 1. physical addressing to 64 bit boundary
> 2. hardware pratical limit
>
> Anyway using arbitraty limits like openbsd do
On Fri, Aug 10, 2012 at 7:35 PM, Friedrich Locke
wrote:
> There are different level of responsaiblity.
>
> 0. setrlimit should be allowed to set any limit the super user wants.
> 1. physical addressing to 64 bit boundary
> 2. hardware pratical limit
>
> Anyway using arbitraty limits like openbsd d
There are different level of responsaiblity.
0. setrlimit should be allowed to set any limit the super user wants.
1. physical addressing to 64 bit boundary
2. hardware pratical limit
Anyway using arbitraty limits like openbsd does for stack is really
bad design. Using arbitrary limit for data is
On 08/10/2012 06:33 PM, Vijay Sankar wrote:
Quoting Friedrich Locke :
Hi,
i have setted my system resources for a given user via login.conf, but
after the user login the ulimit -a returns different values.
Here is my login.conf entry:
general:\
:coredumpsize=infinity:\
:cputi
Quoting Friedrich Locke :
Hi,
i have setted my system resources for a given user via login.conf, but
after the user login the ulimit -a returns different values.
Here is my login.conf entry:
general:\
:coredumpsize=infinity:\
:cputime=infinity:\
:datasize=infinity:\
5 matches
Mail list logo