James Housley stated:
> Brad Knowles wrote:
> >
> >
> > Unfortunately, none of this seems to be related to my problem of
> > having the error message described, or how I can eliminate this error
> > message.
> >
> housley@cat:~/work/monitors {34} sysctl -a | grep -i file
> kern.maxfiles: 2088
> kern.bootfile: /kernel
> kern.maxfilesperproc: 2088
> kern.corefile: %N.core
> p1003_1b.mapped_files: 0
>
> It looks like updating kern.maxfiles and/or kern.maxfilesperproc should
> do the trick. What are the limits set in /etc/login.conf??
I thought this too, but if I run
sysctl -w kern.maxfiles=4096
sysctl -w kern.maxfilesperproc=4096
Now:
% sysctl kern.maxfiles
kern.maxfiles: 4096
% sysctl kern.maxfilesperproc
kern.maxfilesperproc: 4096
However, limit -h (tcsh builtin) and limits -H still report
descriptors 2088
openfiles 2088
respectively.
Even the manpage for sysctl implies this
Name Type Changeable
kern.maxfiles integer yes
kern.maxfilesperproc integer yes
Am I missing something obvious? Are these values really updated?
S
-----------------------------------------------------------------------
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
