In article <[EMAIL PROTECTED]>,
Louis A. Mamakos <[EMAIL PROTECTED]> wrote:
>
> Is it just me, or did something change?
>
> It seems that now you can't raise resource limits after they've been
> lowered. I've had a 'ulimit -c 0' in my login profile for a while;
> previously when I needed to do debugging, I'd raise the limit to
> something reasonable at the shell prompt, and then debug away.
>
> Now it seems to be the case that once the (e.g,) core limit has been
> lowered, you can't raise it again. Am I just remembering this wrong?
Yep, you're remembering wrong. You can raise the soft limit again,
but not the hard limit. It's even documented in sh(1):
ulimit [-HSacdflmnust] [limit]
Set or display resource limits (see getrlimit(2)). If limit is
specified, the named resource will be set; otherwise the current
resource value will be displayed.
If -H is specified, the hard limits will be set or displayed.
While everybody is allowed to reduce a hard limit, only the supe-
ruser can increase it. The -S option specifies the soft limits
instead. When displaying limits, only one of -S or -H can be
given. The default is to display the soft limits, and to set
both the hard and the soft limits.
If you want to lower the coredumpsize limit temporarily, use the
soft limit like this:
ulimit -Sc 5000
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra & Co., Inc. Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
