Comments for mact.me

Comment on Making the Correct Insanely Difficult by Bruno

Bruno — Wed, 22 Jun 2016 19:36:08 +0000

After a couple of days trying to do the same thing I found this post and it worked perfectly!
Thank you so much!

Comment on Things I did today by john

john — Wed, 22 Apr 2015 08:21:03 +0000

dang those printers…

Comment on Things I did today by Dan

Dan — Wed, 04 Mar 2015 12:39:05 +0000

In reply to julien.

I had been pretty apprehensive, too. But Linode just forced our hand with this downtime. AWS has the same security issue to deal with, but no downtime.

Comment on Things I did today by julien

julien — Wed, 04 Mar 2015 08:14:33 +0000

I have chivers when I think of the time when we’ll move off of Linode… I fear that our MySQL replication “accross” the web will be quite flaky given the volume of transactions 🙁

Comment on Yosemite Upgrade Changes Open File Limit by Dan

Dan — Thu, 01 Jan 2015 18:51:21 +0000

Good catch Kevin. Thanks. Updated the post (and put "-a" on both -- maybe the file already exists).

Comment on Yosemite Upgrade Changes Open File Limit by Open File Limits on Mac OS X (Yosemite) | NSLog();

Open File Limits on Mac OS X (Yosemite) | NSLog(); — Thu, 01 Jan 2015 17:34:59 +0000

[…] Yosemite Upgrade Changes Open File Limit | Yabfog […]

Comment on Yosemite Upgrade Changes Open File Limit by Kevin Currie

Kevin Currie — Mon, 22 Dec 2014 18:46:32 +0000

you need to put a “-a” (append) option to your 2nd tee command above or it overwrites the previous entry, should be:
$echo kern.maxfiles=65536 | sudo tee /etc/sysctl.conf
$ echo kern.maxfilesperproc=65536 | sudo tee -a /etc/sysctl.conf

Comment on Yosemite Upgrade Changes Open File Limit by RZ

RZ — Mon, 01 Dec 2014 15:13:52 +0000

@Pat, I thought I had solved the issue using the instructions on this website: http://docs.basho.com/riak/latest/ops/tuning/open-files-limit/#Mac-OS-X

It says the file limit has been changed when I query it in terminal, but my application I’m trying to run does not actually reflect these “system wide” changes. I also have a sysctl.conf file with the “kern.” info. But I do not currently have a launchd.conf. I will give that a shot and see if it helps. Although if I have a LaunchDaemon to do this already, I’m not sure if the launch.conf file is necessary.

Is it possible that specific applications do not use the system-wide changes? And if so, is there a script I could add to the program to allow it to accept the changes, or to change it only for the launch of the application?

Thanks again!

Comment on Yosemite Upgrade Changes Open File Limit by Pat

Pat — Tue, 18 Nov 2014 17:48:44 +0000

@RZ did you create a new launchd.conf with the correct changes in it? This is the file that controls maxfiles for non shell apps I believe. It’s omitted from the Yosemite instructions but I think is still required. Let us know if that works.

Something I noticed is that even for a minor update (like 10.10.1 that I got today) both sysctl.conf and launchd.conf are wiped completely.

Comment on Yosemite Upgrade Changes Open File Limit by RZ

RZ — Thu, 06 Nov 2014 20:06:56 +0000

No luck with reboot. Maxfiles are not updated when I look at launchctl maxfiles, even though the sysctl.conf is rewritten. Thanks anyway though!