My default max limit is acually unlimited right now when I run launchctl limit maxfiles but I'm going to err on the side of sticking to the instructions provided from basho. The gist this was forked from set the macproc to 2048 which is lower than my current default 10240, so I'm not going to modify that for now. I'm no expert on this stuff, but maybe it sounds reasonable to you too.ฤก2288-2048=10240 (soft limit) (Oh hey what do you know - this is the same number as the kern.maxfilesperproc). For a soft limit, I think subtracting 2048 seems fair also. This seems like a fair max limit given my minimal research on this issue. I would presume this might be the kernels max capacity (probably guesstimated by apple, but still, I have to respect apple's settings). drwxr-xr-x 3 root wheel 102 3 Jun 22:09 Dont Steal Mac OS X.kext drwxr-xr-x 3 root wheel 102 3 Jun 22:09 EAP-KRB.ppp drwxr-xr-x 3 root wheel 102 11 May 14:40 EAP-RSA.ppp drwxr-xr-x 3 root wheel 102 3 Jun 22:09 EAP-TLS.ppp drwxr-xr-x 3 root wheel 102 3 Jun 22:39 GeForce.kext drwxr-xr-x 3 root wheel 102 3 Jun 22:39 GeForceAIRPlugin. How I modified limits for my 2013 Macbook air (running sierra): run sysctl -a | grep kern.maxfiles this may show you: kern.maxfiles: 12288 If your system is configured correctly, you should see that maxfiles has been set to 200000. At this point, you can restart your computer and enter ulimit -n into your terminal. Like the plist files, your bashrc or similar file should have -rw-r-r- permissions. In addition to setting these limits at the system level, we recommend setting the at the session level as well by appending the following lines to your bashrc, bashprofile, or analogous file: While the steps explained above will cause system-wide open file limits to be correctly set upon restart, you can apply them manually by running launchctl limit. This permissions should be in place by default, but you can ensure that they are in place by running sudo chmod 644. Both plist files must be owned by root:wheel and have permissions -rw-r-r.
0 Comments
Leave a Reply. |