Simple example script to load multiples instances of mega.co.nz client on linux.

load_mega_instances.sh

#!/bin/sh

for d in */ ; do
        HOME=$(pwd)/$d;
        echo $d;
        # Remove the comment by your need 
        # megasync                    # first run (configure client by client at once)
        # megasync 2> /dev/null &     # load all clients at non blocking way

done

This script will open a mega instance in every folder located in directory path of sh script is located. You should modify by you own. You have to figure out that to load multiples instances of mega you should just set $HOME variable before launching the application.

You might want to check out my simple script based on yout gist: https://github.com/NicoVarg99/MEGA-Instances

Cool

This script will open a mega instance in every folder located in directory path of sh script is located. You should modify by you own. You have to figure out that to load multiples instances of mega you should just set $HOME variable before launching the application.

Hi sir, sorry for bothering. I am trying to adjust your script to use mega-cmd instead of megasync (have a really slow notebook, so running multiple instances of megasync with the script of @NicoVarg99 loads it a lot). Can you please quickly explain how to set the $HOME variable properly? I tried to do that myself (without having any knowledge what I am doing), but stuck with only one account. For example, a have a script.sh and Folder1, Folder2 and Folder3 near it. Don`t you realise what should be changed in the script to launch 3 instances of mega-cmd? Thank you very much

This script will open a mega instance in every folder located in directory path of sh script is located. You should modify by you own. You have to figure out that to load multiples instances of mega you should just set $HOME variable before launching the application.

Hi sir, sorry for bothering. I am trying to adjust your script to use mega-cmd instead of megasync (have a really slow notebook, so running multiple instances of megasync with the script of @NicoVarg99 loads it a lot). Can you please quickly explain how to set the $HOME variable properly? I tried to do that myself (without having any knowledge what I am doing), but stuck with only one account. For example, a have a script.sh and Folder1, Folder2 and Folder3 near it. Don`t you realise what should be changed in the script to launch 3 instances of mega-cmd? Thank you very much

mega-cmd works for the first instance only.
You should close all mega-cmd first.

This script will open a mega instance in every folder located in directory path of sh script is located. You should modify by you own. You have to figure out that to load multiples instances of mega you should just set $HOME variable before launching the application.

Hi sir, sorry for bothering. I am trying to adjust your script to use mega-cmd instead of megasync (have a really slow notebook, so running multiple instances of megasync with the script of @NicoVarg99 loads it a lot). Can you please quickly explain how to set the $HOME variable properly? I tried to do that myself (without having any knowledge what I am doing), but stuck with only one account. For example, a have a script.sh and Folder1, Folder2 and Folder3 near it. Don`t you realise what should be changed in the script to launch 3 instances of mega-cmd? Thank you very much

mega-cmd works for the first instance only. You should close all mega-cmd first.

So its impossible to run 3 instances of mega-cmd simultaneously, am I right?

The last update of @NicoVarg99's script is already 6 years old. I made a new version with some modifications and checks and I hope you find it useful

MEGAsync Instances (start | stop | status)

# Dependencies:
# sudo apt install zenity libatk-adaptor libgail-common libgtk2.0-0 (or libgtk2.0-0t64 for Ubuntu 24.04)
# Download and Install:
# sudo wget -O /usr/bin/msyncs https://raw.githubusercontent.com/maravento/vault/master/scripts/bash/msyncs
# sudo chmod 755 /usr/bin/msyncs
# Run:
# msyncs start|stop|status

PD: At the moment it is only compatible with Ubuntu 22.04/24.04 x64 (I have not been able to verify it on other distros)