{"id":40447,"date":"2023-08-25T14:22:49","date_gmt":"2023-08-25T18:22:49","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=40447"},"modified":"2023-09-04T14:29:47","modified_gmt":"2023-09-04T18:29:47","slug":"macos-13-5-no-longer-allows-setting-system-wide-ulimits","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/08\/25\/macos-13-5-no-longer-allows-setting-system-wide-ulimits\/","title":{"rendered":"macOS 13.5 No Longer Allows Setting System-Wide ulimits"},"content":{"rendered":"

axeman12<\/a> (via Hacker News<\/a>):<\/p>\n

As of the newest MacOs releases (11.7.9, 12.6.8, and 13.5) I am no longer able to increase the ulimit of my computer using the strategies outlined<\/a> here<\/a>.<\/p>

[…]<\/p>

This is relevant for me as I am using Vite which is currently broken and blocks me from developing locally. It is mentioned in their troubleshooting page<\/a> that Vite causes a large number of open files and how to increase the limit.<\/p><\/blockquote>\n\n

Quinn<\/a>:<\/p>\n

\n

Changing a system-wide setting to work around an issue with a specific product seems rather extreme. A better option would be to change it for that process specifically. If you have access to the code, add a call to setrlimit<\/code>. If you don’t have access to the code, you could work out how the code is launched and add a wrapper, using either a shell script (and hence ulimit<\/code>) or a native executable (setrlimit<\/code> again).<\/p>\n<\/blockquote>\n\n

Apple Staff<\/a>:<\/p>\n

This is in fact a bug. Good news is, there’s a workaround!<\/p>\n

launchctl limit maxfiles 256 unlimited\nlaunchctl limit maxfiles 128000 524288<\/pre><\/blockquote>\n
However, one commenter says this doesn’t work. What does seem to work is turning off System Integrity Protection.<\/p>\n\n
Previously:<\/p>\n