![]() I'll be using folders to partition between applications (not strictly necessary with mktemp but it'll be a bit more tidy separating them out, and with the folders pre-created it'll be dead easy). I've come around to the folders option as well. I'll get my scripts/apps sorted and do some more testing. Having it as an option per mount in the manager might work, but it's a niche requirement at best - I can't imagine it would be worth the effort to add.Īs I said, looking good - very good :). I thought about suggesting auto-deleting the mounts on exit but I can definitely see the downside of losing everything from your tmpdisk if you exit accidentally. As soon as I've converted my apps and scripts I will test more thoroughly, and also do more with the autocreate manager. I'm dependent on having a tmpdisk at /Volumes/tmp at the moment so I haven't swapped over to the new version since I don't think you can do that with the new version. Having said that, I'll only be setting the size once, since I'll be using autocreate (I've already set it up) - so really an unnecessary complication, I guess. This works pretty well for me as the memory isn't actually used until you start filling up the disk and it isn't limited unnecessarily. The only improvement I can currently think of, is to allow the size to be unspecified for tmpfs which will default the max size to 1/2 your memory (I think.). On the whole I suspect that the folder feature is probably an unnecessary complication, but might well be useful for other use cases than mine. The mktemp approach does make cleanup easy, though. OTOH, taking advantage of that feature may be a better solution than what I'm currently doing. The folders option is not something I'd use since the work directories I was talking about are all created using mktemp - apologies if I misled you at all and you put that in for me. I guess it's because I've never used the terminal app on this machine (I use iterm usually). The first time I used it, it opened a terminal window, and then the dialog for the password, but since that first time, it now only opens the dialog. It would be nice to have it in tmpdisk but I understand your position, and the script works adequately well, so no pressure :). Given the amount of churn creating and deleting the work directories and their contents I also don't really want to use my SSD for it either.Ĭurrently I'm running a script to create the tmpfs but I miss the convenience of having tmpdisk automatically manage it for me. OTOH having a max of 2GB available (which is how I used to do it with tmpdisk before finding mount_tmpfs) causes a lot of jobs to fail unnecessarily. I don't really want to pre-allocate the whole 16GB from memory since it is rare that the whole 16GB is required. ![]() ![]() Most of the time the process is only using a few kilobytes but every so often a lot of jobs will arrive and it may use up to 16GB. Each job is given its own work directory within the temporary disk I have mounted. I have a service running on my Mac which will run jobs on behalf of other devices on the network. The second item is the bit that makes it most useful for me.
0 Comments
Leave a Reply. |