Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

I'm trying to mount a RAM disk on startup with this:

/Users/Aram/Development/Tools/ramdisk.sh

diskutil erasevolume HFS+ "RamDisk" `hdiutil attach -nomount ram://800000`

com.aram.ramdisk.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" 
        "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>Label</key>
        <string>com.aram.ramdisk</string>
        <key>ProgramArguments</key>
        <array>
            <string>/bin/sh</string>
            <string>/Users/Aram/Development/Tools/ramdisk.sh</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
    </dict>
</plist>

And then running:

  • sudo chown root:wheel /Library/LaunchDaemons/com.aram.ramdisk.plist
  • sudo launchctl load -w /Library/LaunchDaemons/com.aram.ramdisk.plist

But I get these in the console:

1/08/12 1:29:25.982 PM fseventsd[64]: could not open <</Volumes/RamDisk/.fseventsd/fseventsd-uuid>> (No such file or directory)
1/08/12 1:29:25.982 PM fseventsd[64]: log dir: /Volumes/RamDisk/.fseventsd getting new uuid: 102D7293-F1F1-4640-AA50-D547C365339F

1/08/12 1:29:24.561 PM sudo[1193]:     Aram : TTY=ttys000 ; PWD=/Library/LaunchDaemons ; USER=root ; COMMAND=/bin/launchctl load -w /Library/LaunchDaemons/com.aram.ramdisk.plist

1/08/12 1:40:17.052 PM com.apple.launchd[1]: (com.aram.ramdisk) Throttling respawn: Will start in 8 seconds

It works if I set KeepAlive to true, but then it creates a RAM disk every 10 seconds.

Is there a way to delay the script for 10 seconds before running?

share|improve this question
    
Which version of OSX are you using? –  de_an777 Aug 1 '12 at 5:24
    
Mountain Lion... –  Aram Kocharyan Aug 1 '12 at 13:33
add comment

2 Answers

You can delay the execution of the diskutil command in your ramdisk.sh script by prepending the line sleep 10.

Sleep suspend the execution for an interval of time, in seconds.

Your new ramdisk.sh becomes:

sleep 10
diskutil erasevolume HFS+ "RamDisk" `hdiutil attach -nomount ram://800000`

Update#1: launching the ramdisk.sh every 10 seconds and only creating the RAM disk when it is not there, is a workaround. See this example script for such a conditional check:

sleep 10
RD=RamDisk
if [ ! -e "/Volumes/$RD" ];  then
    diskutil erasevolume HFS+ "$RD" `hdiutil attach -nomount ram://800000`
fi

Your error might be caused because /Volumes is not already created in the boot process at the moment your launchd job is executed. Thefore you could first check for the existence of /Volumes before even further executing the script, like:

if [ -e "/Volumes" ];  then
    RD=RamDisk
    if [ ! -e "/Volumes/$RD" ];  then
        diskutil erasevolume HFS+ "$RD" `hdiutil attach -nomount ram://800000`
    fi
fi

And when the creation succeeds you might want to unload your com.aram.ramdisk.plist from launchctl until the next boot.

share|improve this answer
1  
This might be a good use for the QueueDirectories keyword in the launchd configuration (to make sure /Volumes is available) –  patrix Aug 1 '12 at 8:21
add comment
up vote 0 down vote accepted

Using Pro Backup's great answer I put this together and it works:

#!/bin/bash
NAME="RamDisk"
while [ ! -d /Volumes ]
do
    echo "waiting..."
    sleep 2
done
if [ ! -d /Volumes/$NAME ]; then
    echo "creating ramdisk..."
    diskutil erasevolume HFS+ $NAME `hdiutil attach -nomount ram://800000`
fi

I needed this so that my browser wouldn't cache to my SSD, so I deleted this:

rm -rf /Users/Aram/Library/Caches/Google/Chrome/Default

And created a symlink:

ln -s /Volumes/RamDisk/ /Users/Aram/Library/Caches/Google/Chrome/Default

EDIT:

I just added the script as a startup application in user settings on my mac, always works, though leaves a terminal open. No big deal for me.

share|improve this answer
    
Why wouldn't you want your browser to cache to SSD? For more space? –  Shane Hsu Apr 14 '13 at 5:28
1  
Mostly to reduce tiny writes every time the cache changes. I need the cache to speed up browsing, and I use the computer all day, so having it in the RAM doesn't have any impact other than reducing usage of the disk. Chances are the life expectancy difference won't affect me, but over many years there may be a difference. –  Aram Kocharyan Apr 14 '13 at 5:33
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.