Bash script to check multiple registered accounts in mega.nz cloud using megatools.

For automated jobs use mmega_cron.sh

If you want to save all the information about your files in a database you can check out this others scripts:

• mmega_pg. Using PostgreSQL as database (preferred).
• mmega_my. Using MySQL as databse (abandoned but still working).

Check free space and files of several registered accounts in mega.nz cloud using the nice code megatools written by megaus.

      mmega --config <file> --mode <df|status|up|down|sync> [options]       
      mmega --search <dir> <name> [options]         

NOTE: The short descriptors -c -m and -s are also accepted.

• megatools
• torsocks (if Tor is used)
• gpg (if encryption is used)
• curl (if IP is retrieved)
• dig (if DNS is retrieved)
• some bash specific commands

This script works in two styles, 'config file' style or 'search' style.

It reads a config file with account's parameters (login and directories) for each account (see below). This file is parsed to check common mistakes in format (five fields comma separated). Using this file and the suite megatools the script checks the free space available for each account. If mode status is used (see below) it compares files in local and remote directories and summarizes the accounts state. It prints the free space and the number of files to be downloaded or uploaded for each account. If modes sync|down|up are used these files are then synchronized accordingly.

It contains in each line the account's parameters. The structure is comma separated with 5 fields:

name1,username1,passwd1,local_dir1,remote_dir1,
name2,username2,passwd2,local_dir2,remote_dir2,
name3,username3,passwd3,local_dir3,remote_dir3,
...

      mmega --config <file> --mode <df|status|up|down|sync> [options]

NOTE: status mode doesn't show the files, only the number of files. If you want to check what files have been downloaded or uploaded you should use --files option (see below).

NOTE: When using up|down|sync modes mega.nz site and megatools provide a security method to never overwrite the files. If there are discrepancies, the files are marked with a number (that indicates the node) and the word conflict. You will have to check 'by hand' these discrepancies (See megaus code at github). However if two copies of the same file are named the different way they will be considered as two different files.

      mmega --search <dir> <name> [options]

Megatools allows a file with account login parameters to avoid writing them each time (see megatools manual). If you have several of them, you can you use this style to find them and consult the accounts (and the path to these config files). It only retrieves Free, Used and Total space in cloud. It prints Free, Total, username and path to config file for each account. Finally it summarizes this information.

The search dir is mandatory. The name can be left in blank (preferred method) or you can pass it as argument. When asked for the name you should use wildcards to search for a pattern in your accounts (as .megarc*) but if you pass it as argument do not use wildcards, the script will add * to this name to search for a pattern and not a specific name.

Search mode only accept the options --tor on|off (see below)

NOTE: The short descriptors -t -f and -p are also accepted.

The whole config file can be encrypted if the private key is in the system's gpg keyring. If private key is password-protected you will be asked for it. For a cron job you can use a password-less key or pass the password as argument.

The script uses a color code to summarizes the state of accounts (see screenshots). Thus synchronized accounts are shown in green, unsynchronized in yellow and fail in red. The fail state means there were errors with directories (local or remote). The errors parsing the config file are shown in black. For cron mail reporting this color code can be annoying. If you want you can set colors variables to nothing in the beginning of script or you can use the new mmega_cron.sh script which has been adapted for a cron job.

IMP: Check that MEGACOPY and MEGADF variables (lines 94 adn 95) point to your binaries (usually in /usr/bin/ or /usr/local/bin). If they are set wrong all accounts give error.

The code is far from being optimized, is a simple script that I use as cron job to maintain a regular contact with my accounts after the change of policy mega.nz where unused accounts are eliminated.

Check status for accounts in config file accounts_mega.gpg and show the files:

      mmega --config accounts_mega.gpg --mode status --files                     (gpg will ask)
      mmega --config accounts_mega.gpg --mode status --files --passwd            (script will ask)
      mmega --config accounts_mega.gpg --mode status --files --passwd "PASSWORD"

Synchronize all unsyncronized accounts in the config file accounts_mega.gpg using Tor:

      mmega -c accounts_mega.gpg -m sync --tor on --passwd

Check all space available for all accounts in accountsmega config file:

      mmega -c /home/user/accountsmega -m df

Search for megarc* files in /home/user/ directory and show accounts and connection data:

      mmega --search /home/user/ megarc -t off

Cron job format