Vivek Khera stated:
> >>>>> "SO" == Sean O'Connell <[EMAIL PROTECTED]> writes:
>
> SO> I thought this too, but if I run
>
> SO> sysctl -w kern.maxfiles=4096
> SO> sysctl -w kern.maxfilesperproc=4096
>
> SO> Now:
>
> SO> % sysctl kern.maxfiles
> SO> kern.maxfiles: 4096
> SO> % sysctl kern.maxfilesperproc
> SO> kern.maxfilesperproc: 4096
>
> SO> However, limit -h (tcsh builtin) and limits -H still report
>
> SO> descriptors 2088
> SO> openfiles 2088
>
> [ ... ]
>
> SO> Am I missing something obvious? Are these values really updated?
>
> Did you logout and back in? I don't think upping the system-wide
> limits will dynamically update the limits given to processes that are
> already started. Logging in again will cause your process (ie, the
> shell) to have its resource limits set to the current hard limits.
>
> ps: Go Duke!!! I really miss the place. ;-(
Vivek-
D'oh. Sean gets the proverbial pointy hat on that. I did a login
from an xterm -ls and it worked. I have too many open windows at
the moment.
So for the matter at hand, I would suppose that stopping and restarting
innd would be all that is needed.
S
PS. And to think I give people a "hard time" about group membership
and the need to logout and log back in.
-----------------------------------------------------------------------
Sean O'Connell Email: [EMAIL PROTECTED]
Institute of Statistics and Decision Sciences Phone: (919) 684-5419
Duke University Fax: (919) 684-8594
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
