I bought MyCloud device few years ago, I am using as incremental backup station on my network. Device itself is far away from being a perfect product to be honest. As I love backing up my own files&photos, I prefer to back up my back up disk…

After the short introduction, let me tell you my problem&solution. Normally WebUI itself does not allow you to create a scheduled task for backing up your MyCloud to USB. However, what you can do is you can create a symbolic link. Then you can show that location…

Start from here

Create a symbolic link

ln -s /mnt/USB/USB1_b1/FullBackUp/ USB_DISK

After this go to Internal Backups

Here, click “create a job”. Then you can modify the Destination path by doing inspect element (destination path) on Google Chrome(or any other browser allows you to do that). But be careful there is more than one field you need to change

After that you can simply run your script to test, normally it creates a folder first (with the job name) then started copying files where symbolic link is located. You can also set reoccurrence as you like…

I tested it on OS (2.31.204) and works flawlessly…
I hope it helps.

Egemen

I am writing this post to debug slow zsh…

Very first thing is to show how slow your zsh is. For that lets run 10 times and see how long does it take to get terminal up and running…

for i in $(seq 1 10); do /usr/bin/time $SHELL -i -c exit; done

Obviously, I assume your default $SHELL is set as Zsh…

Okay, we observed it takes some time with the previous command. Let’s do a bit more debugging. Let’s run ZSH in debug mode:

zsh -xv

This will give you more information it shows the process as the package loaded. So in my case, the rbenv plugin was extremely slow. As I don’t necessarily to use that plugin so I simply disabled by removing the plugin from the plugin section of file ~/.zshrc

I think you should able to reduce start-up time by using the described methodology. However, in order to get more fine-grained approach you can add the following link at the beginning of the very same file ~.zshrc

zmodload zsh/zprof

And add the next line add the end of the same file.

zprof

Close and save and get a new terminal you should learn more details with zprof.  Take your time to analyse the output…

Again in my case, I can see compinit takes so much time to load. For that I did a bit of googling and reached the following url:

https://gist.github.com/ctechols/ca1035271ad134841284

As aksh1618 indicated, I edited oh-my-zsh.sh file what is stored in ~/.oh-my-zsh/oh-my-zsh.sh. First I found the following line:

# Else, enable and cache completions to the desired file.
else
compinit -d "${ZSH_COMPDUMP}"
fi
else
compinit -i -d "${ZSH_COMPDUMP}"
fi

And changed to

# Else, enable and cache completions to the desired file.
else
compinit -C -d "${ZSH_COMPDUMP}"
fi
else
compinit -C -d "${ZSH_COMPDUMP}"
fi

Moreover, add the following line to ~/.oh-my-zsh/oh-my-zsh.sh

find $HOME -maxdepth 1 -iname '.zcompdump*' -mtime 1 -delete | grep -q "." && source $HOME/.zshrc

As aksh1618, this will make oh-my-zsh.sh recreate any compdump older than a day. In my case, you can see the startup performance improved (check compinit). After your debug is finished, you can remove related zprof lines (at the beginning/end your ~.zshrc) in order to stop printing debug information.

I hope it helps you to reduce your terminal’s startup time…