# MEGAcmd User Guide This document relates to MEGAcmd version 2.1.1. It contains introductory information and the [Command Summary](#command-summary), with links to detailed command descriptions. ### What is it A command line tool to work with your MEGA account and files. The intent is to offer all the MEGA account functionality via command line. You can run it in [interactive](#interactive) mode where it processes all commands directly, or you can run its [scriptable](#scriptable) commands from your favourite Linux or Mac shell such as bash, or you can even run its commands in a Windows command prompt. And of course you can write scripts using those scriptable commands. Here is an example of downloading a file using MEGAcmd. In this case we are downloading a file specified by a public link, which does not require being logged in:
``` mega-get https://mega.nz/#F!ABcD1E2F!gHiJ23k-LMno45PqrSTUvw /path/to/local/folder ``` Note:- If you get any error like this one ``` Event not found ``` In link put ```\``` in front of every ```!``` for example ``` mega-get https://mega.nz/#F\!ABcD1E2F\!gHiJ23k-LMno45PqrSTUvw /path/to/local/folder ``` And here is an example of uploading a file using MEGAcmd, and making a link available to share it, that will expire after 10 minutes.
``` mega-put /path/to/my/temporary_resource /exportedstuff/ mega-export -a /exportedstuff/temporary_resource --expire=10M | awk '{print $4}' ``` And here is an example of the power of using [scriptable](#scriptable) MEGAcmd commands in bash. In this case we are going to share some promotional videos previously uploaded to MEGA:
``` for i in $(mega-find /enterprise/video/promotional2015/may --pattern="*mpeg") do mega-export -a $i | awk '{print $4}'; done ``` In addition to running commands on request, MEGAcmd can also be configured to [synchronise](#synchronisation-configurations) folders between your local device and your MEGA account, or perform regular [backups](#backup-configurations) from your device to your MEGA account. In order to enable synchronisation and backup features, and for efficiency running commands, MEGAcmd runs a server process in the background which the MEGAcmd shell or the script commands forward requests to. The server keeps running in the background until it is told to close with the [`quit`](#quit) command. If you want it to keep running when you quit the interactive shell (to keep sync and backup running for example), use `quit --only-shell`. Working with your MEGA account requires signing in with your email and password using the [`login`](#login) command, though you can download public links or upload to public folders without logging in. Logging in with your username and password starts a [Session](#session), and causes some of your account such as the folder structure to be downloaded to your [Local Cache](#local-cache). ### Where can you get it For Linux, Mac, or Windows: Download it from the MEGA.nz website: https://mega.nz/cmd
We are also building it for some NAS systems, please check your provider's App Store. ### What can you do with it The major features are * Move files around inside your MEGA account or between MEGA and your PC using command line tools. * Use those same commands in scripts to manage your files. * Set up synchronization or a backup schedule between a folder on your machine, and a folder on your MEGA account. (use the [`sync`](#sync) or [`backup`](#backup) commands). * Set up WebDAV access to files in your MEGA account (use the [`webdav`](#webdav) command). * [Linux only] Set up a FUSE mount point to seamlessly access files in your MEGA account (use the [`fuse-add`](#fuse-add) command). See our Help Centre pages for the basics of getting started, and friendly examples of common usages with plenty of pictures: https://mega.nz/help ## Terminology and Descriptions ### Interactive Interactive refers to running the MEGAcmd shell which only processes MEGA commands. You invoke commands by typing and pressing Enter. MEGAcmd shell provides a lot of feedback about what it's doing. You can start the MEGAcmd shell with `mega-cmd` (or `MEGAcmd` on Windows). You can then issue commands like `ls` directly:
`ls /my/account/folder`
or you can get a list of available commands with:
`help`
or you can get detailed information about any particular command by using the `--help` flag with that command:
`ls --help`
Autocompletion (pressing tab to fill in the remainder of a command) is available in interactive mode. ### Scriptable Scriptable refers to running the MEGAcmd commands from a shell such as bash or the windows powershell. If the PATH to the MEGAcmd commands are not yet on the PATH in that shell, you'll need to add it. You can then issue commands like `ls` by prefixing them with the `mega-` prefix:
`mega-ls /my/account/folder`
or you can get a list of available commands with:
`mega-help`
or you can get detailed information about any particular command by using the `--help` flag with that command:
`mega-ls --help`
Scriptable commands can of course be used in scripts to achieve a lot in a short space of time, using loops or preparing all the desired commands ahead of time. If you are using bash as your shell, the MEGAcmd commands support auto-completion. ### Contact A contact is someone (identified by their email address) that also has a MEGA account, who you can share files or folders with, and can chat with on MEGAchat. ### Remote Path This refers to a file or a folder stored in your MEGA account, or a publicly available file or folder in the MEGA cloud. Remote paths always use the '/' character as the separator between folder and file elements. Some MEGAcmd commands allow the use of regular expressions in remote paths. You can check if the command supports those by using the `--help` flag with the command. If you use these in the [scriptable](#scriptable) way, you need to escape characters that would otherwise be intercepted and interpreted by the shell. Paths to folders shared to you from another person start with their email and a : character, see the example at ([example](#shared-folders-example)) ### Local Path This refers to a file or folder on the PC or device that MEGAcmd is running in. ### Session When you log in with your email and MEGA account password, that creates a session. The session exists until you log out of it or kill it from another client. In MEGAcmd, use `whoami -l` to see all your open sessions across all devices, and use `killsession` to close them. You can use other MEGA clients such as the phone app, or webclient to close these also. Devices that were using a killed session will have their connection to MEGA closed immediately and will no longer have access to your account, until you log in on them again. Syncs, backups, and webdavs are specific to a session, so logging out will cause them to be cancelled. ### Local Cache Logging in with MEGAcmd creates your Local Cache, a subfolder of your home folder. MEGAcmd downloads and stores some data in your Local Cache relating to your account, such as folder structure and contacts, for performance reasons. The MEGAcmd background server keeps the local cache up to date when changes to your account occur from other clients. The cache does contain a way for MEGAcmd to access your MEGA account when it starts up again if you have not specifically logged out. The Local Cache also contains information from your Session, including sync, backup, and webdav configurations. Logging out cleans the Local Cache, but also closes your session and the sync, backup, and webdav configurations are wiped. ### Synchronisation configurations MEGAcmd can set up a synchronisation between a folder on your local machine and a folder in your MEGA account, using the [`sync`](#sync) command. This is the same mechanism that MEGAsync uses. The synchronisation is two-way: the folders you nominate to be synced will mirror any action! Whatever you add or delete in your sync folder on your device gets added or deleted in your sync folder in your MEGA account. And additions or deletions in your synced folder in your MEGA account will similarly be applied to your local synced folder. Files that are removed from sync folders are moved to a hidden local folder (Rubbish/.debris inside your local sync folder, or SyncDebris folder in the Rubbish Bin of your MEGA account). Here is a very simple example of setting up a synchronisation with MEGAcmd:
``` sync /path/to/local/folder /folder/in/mega ``` You can set up more than one pair or folders to be synced, and you can also set a sync from another device to the same folder, to achieve folder synchronisations between different devices. The changes are sent via your MEGA account rather than directly between the devices in that case. Additional information about synchronising folders is available in our Help Centre: https://mega.nz/help/client/megasync/syncing ### Backup configurations MEGAcmd can set up a periodic copy of a local folder to your MEGA account using the [`backup`](#backup) command. Here is a simple example that will back up a folder immediately and then at 4am each day, keeping the 10 most recent backups:
``` backup /path/mega/folder /remote/path --period="0 0 4 * * *" --num-backups=10 ``` For further information on backups, please see the [`backup`](#backup) command and the [tutorial](contrib/docs/BACKUPS.md). ### WebDAV configurations MEGAcmd can set up access to folders or files in your MEGA account as if they were local folders and files on your device using the [`webdav`](#webdav) command. For example making the folder appear like a local drive on your PC, or providing a hyperlink a browser can access, where the hyperlink is to your PC. For further information on WebDAV, please see the [`webdav`](#webdav) command and the [tutorial](contrib/docs/WEBDAV.md ### FUSE mount point If you use Linux, MEGAcmd can set up access to folders or files in your MEGA account as if they were local folders and files on your device using Filesystem in User Space via [`fuse-add`](#fuse-add) command. For further information on FUSE, please see the [`fuse-add`](#fuse-add) command and the [tutorial](contrib/docs/FUSE.md). ### Linux On Linux, MEGAcmd commands are installed at /usr/bin and so will already be on your PATH. The interactive shell is `mega-cmd` and the background server is `mega-cmd-server`, which will be automatically started on demand. The various scriptable commands are installed at the same location, and invoke `mega-exec` to send the command to `mega-cmd-server`. If you are using the scriptable commands in bash (or using the interactive commands in mega-cmd), the commands will auto-complete. ### Macintosh For MacOS, after installing the dmg, you can launch the server using **MEGAcmd** in Applications. If you wish to use the client commands from MacOS Terminal, open the Terminal and include the installation folder in the PATH.
Typically:
```
export PATH=/Applications/MEGAcmd.app/Contents/MacOS:$PATH
```
And for bash completion, source `megacmd_completion.sh` :
```
source /Applications/MEGAcmd.app/Contents/MacOS/megacmd_completion.sh
```
### Windows
Once you have MEGAcmd installed, you can start the [interactive](#interactive) shell from the Start Menu or desktop icon. On windows the interactive shell executable is called `MEGAcmdShell.exe` and the server is `MEGAcmdServer.exe`.
On Windows 7, we recommend using the MEGAcmd shell from inside PowerShell for a better user experience (and you can do this on other Windows platforms also). You can start powershell from the Start Menu and then execute these commands to start it:
```
$env:PATH += ";$env:LOCALAPPDATA\MEGAcmd"
MEGAcmdShell
```
For [scriptable](#scriptable) usage, the MEGAcmd commands are provided via installed .bat files which pass the command to the MEGAcmdServer.exe. Provided you have set the PATH as above, you can use these like normal command line tools in PowerShell:
```
$env:PATH += ";$env:LOCALAPPDATA\MEGAcmd"
mega-cd /my/favourite/folder
mega-ls
```
Or in Command Prompt:
```
set PATH=%LOCALAPPDATA%\MEGAcmd;%PATH%
mega-cd /my/favourite/folder
mega-ls
```
And of course those can be invoked in your own .bat or .cmd files.
Autocompletion is not available for the scriptable commands, but is in the interactive shell.
Unicode is supported though it currently in the interactive shell it needs to be switched on, and to have a suitable font selected; please execute `help --unicode` for the latest information. There are plans to improve this. Please report any issues experienced to our support team.
### NAS Support
We have released packages for QNAP and Synology, which you can download and install from the App Center in QNAP, and the Package Center in Synology. In QNAP, please make sure to turn on "Enable home folder for all users" from the control panel, and set HOME=/share/homes/
MEGA CMD> signup eg.email_1@example.co.nz --name="test1"
New Password:
Retype New Password:
Account
#### Logging-in and contacts
MEGA CMD> login eg.email_1@example.co.nz
Password:
[SDK:info: 23:19:14] Fetching nodes ...
Fetching nodes ||########################################||(38/38 MB: 100.00 %)
[SDK:info: 23:19:17] Loading transfers from local cache
[SDK:info: 23:19:17] Login complete as eg.email_1@example.co.nz
#### Adding a contact and viewing
eg.email_1@example.co.nz:/$ invite eg.email_2@example.co.nz
Invitation to user: eg.email_2@example.co.nz sent
eg.email_1@example.co.nz:/$ showpcr
Outgoing PCRs:
eg.email_2@example.co.nz (id: 47Xhz6wvVTk, creation: Thu, 26 Apr 2018 11:20:09 +1200, modification: Thu, 26 Apr 2018 11:20:09 +1200)
eg.email_1@example.co.nz:/$ logout
Logging out...
MEGA CMD> login eg.email_2@example.co.nz
Password:
[SDK:info: 23:21:10] Fetching nodes ...
[SDK:info: 23:21:12] Loading transfers from local cache
[SDK:info: 23:21:12] Login complete as eg.email_2@example.co.nz
eg.email_2@example.co.nz:/$ showpcr
Incoming PCRs:
eg.email_1@example.co.nz (id: 47Xhz6wvVTk, creation: Thu, 26 Apr 2018 11:20:09 +1200, modification: Thu, 26 Apr 2018 11:20:09 +1200)
eg.email_2@example.co.nz:/$ ipc 47Xhz6wvVTk -a
Accepted invitation by eg.email_1@example.co.nz
eg.email_2@example.co.nz:/$ users
eg.email_1@example.co.nz, visible since Thu, 26 Apr 2018 11:22:02 +1200
eg.email_2@example.co.nz:/$ userattr --user=eg.email_1@example.co.nz
firstname = test1
ed25519 = 5Xl2-mUtsZkaATmSS88Ncepju5805uw66Hfdh_-SwpE
cu25519 = ejoYtpaJIZvlpmPsYviIa6tNvPTdVjfkYf9G1k8PKgM
rsa = AAAAAFrhDPPMS1AXAhJwScpJ_GKqFUJ42uIIcwxLp5RIalkWtsa5j87u2LFhoZlI_rHIzGXrdsbywgs7Msisw0CjodrtwtME
cu255 = AAAAAFrhDPPWUOP2tNByV72zU4M3EKNoddyVCT13VkkouMldniR2UZtLrPjUjUeOZOLvOL7H1C0W0Q_b3QqYSvAKo775pUwD
eg.email_2@example.co.nz:/$ logout
Logging out...
MEGA CMD> login eg.email_1@example.co.nz
Password:
[SDK:info: 23:24:26] Fetching nodes ...
[SDK:info: 23:24:27] Loading transfers from local cache
[SDK:info: 23:24:27] Login complete as eg.email_1@example.co.nz
eg.email_1@example.co.nz:/$ users
eg.email_2@example.co.nz, visible
eg.email_1@example.co.nz:/$ userattr --user=eg.email_2@example.co.nz
firstname = test2
ed25519 = M7SLy2RajwUAvynxJQaVkhe6hxGpbwJmvve3dgl8B1o
cu25519 = VaXluGS2c5xbo0xOHHJciqLRxwMaWZHVK8iuxtlCBTk
rsa = AAAAAFrhDWemabQ4JAOtP7zcoy6m74PsFTFCbj04Zh4G8K_TZB5Sm9T5Xj9CXYzwWnpfRd1McPdDouKdsASQ6Er7i4Y4LpEA
cu255 = AAAAAFrhDWcXE_7AHZmvxk5Hk0G7V65UnvFO42tb1gM9SYy3BpsMCas0X-pbqkYwf6_2eBG-ZLvkonGfXB3DWonWNvnVehIB
### Node operations
#### Getting user info
MEGA CMD> login eg.email_1@example.co.nz
Password:
[SDK:info: 23:43:14] Fetching nodes ...
[SDK:info: 23:43:14] Loading transfers from local cache
[SDK:info: 23:43:14] Login complete as eg.email_1@example.co.nz
eg.email_1@example.co.nz:/$ whoami -l
Account e-mail: eg.email_1@example.co.nz
Available storage: 50.00 GBytes
In ROOT: 146... KBytes in 1 file(s) and 0 folder(s)
In INBOX: 0.00 Bytes in 0 file(s) and 0 folder(s)
In RUBBISH: 0.00 Bytes in 0 file(s) and 0 folder(s)
Total size taken up by file versions: 0.00 Bytes
Pro level: 0
Subscription type:
Account balance:
Current Active Sessions:
* Current Session
Session ID: m3a8eluyPdo
Session start: 4/26/2018 11:43:12 AM
Most recent activity: 4/26/2018 11:43:13 AM
IP: 122.56.56.232
Country: NZ
User-Agent: MEGAcmd/0.9.9.0 (Windows 10.0.16299) MegaClient/3.3.5
-----
1 active sessions opened
eg.email_1@example.co.nz:/$ mount
ROOT on /
INBOX on //in
RUBBISH on //bin
#### Downloading a file
eg.email_1@example.co.nz:/$ ls
Welcome to MEGA.pdf
eg.email_1@example.co.nz:/$ get "Welcome to MEGA.pdf"
TRANSFERING ||################################################################################||(1/1 MB: 100.00 %)
Download finished: Welcome to MEGA.pdf
TRANSFERING ||################################################################################||(1/1 MB: 100.00 %)
#### Uploading a file
eg.email_1@example.co.nz:/$ mkdir my-pictures
eg.email_1@example.co.nz:/$ cd my-pictures/
eg.email_1@example.co.nz:/my-pictures$ put C:\Users\MYWINDOWSUSER\Pictures
TRANSFERING ||################################################################################||(1/1 MB: 100.00 %)
Upload finished: C:\Users\MYWINDOWUSER\Pictures
TRANSFERING ||################################################################################||(1/1 MB: 100.00 %)
#### Creating and navigating directories
eg.email_1@example.co.nz:/my-pictures$ pwd
/my-pictures
eg.email_1@example.co.nz:/my-pictures$ ls
Pictures
eg.email_1@example.co.nz:/my-pictures$ cd Pictures/
eg.email_1@example.co.nz:/my-pictures/my-pictures$ ls
Camera Roll
Feedback
Saved Pictures
megacmdpkg.gif
megacmdpkg_80.gif
megacmdpkg_gray.gif
eg.email_1@example.co.nz:/my-pictures/my-pictures$ pwd
/my-pictures/Pictures
eg.email_1@example.co.nz:/my-pictures/my-pictures$ cd /
eg.email_1@example.co.nz:/$ du -h my-pictures/
FILENAME SIZE
my-pictures: 1.31 MB
----------------------------------------------------------------
Total storage used: 1.31 MB
#### Logging-out
eg.email_1@example.co.nz:/$ logout
Logging out...
MEGA CMD>
### Syncing
email_1@example.co.nz:/$ sync c:\Go go-backup/
Added sync: //?\c:\Go to /go-backup
email_1@example.co.nz:/$ sync
ID LOCALPATH REMOTEPATH RUN_STATE STATUS ERROR SIZE FILES DIRS
WOOmFwZfQwM \\?\c:\Go /go-backup Running Syncing NO 119.13 KB 10 97
email_1@example.co.nz:/$ sync
ID LOCALPATH REMOTEPATH RUN_STATE STATUS ERROR SIZE FILES DIRS
WOOmFwZfQwM \\?\c:\Go /go-backup Running Syncing NO 61.22 MB 1252 463
email_1@example.co.nz:/$ sync
ID LOCALPATH REMOTEPATH RUN_STATE STATUS ERROR SIZE FILES DIRS
WOOmFwZfQwM \\?\c:\Go /go-backup Running Syncing NO 232.94 MB 4942 773
email_1@example.co.nz:/$ sync
ID LOCALPATH REMOTEPATH RUN_STATE STATUS ERROR SIZE FILES DIRS
WOOmFwZfQwM \\?\c:\Go /go-backup Running Synced NO 285.91 MB 7710 1003
Then, on a windows cmd prompt:
C:\Users\ME>rmdir /s c:\go\blog
c:\go\blog, Are you sure (Y/N)? Y
Back in MEGAcmd (the update has been applied to MEGA already):
email_1@example.co.nz:/$ sync
ID LOCALPATH REMOTEPATH RUN_STATE STATUS ERROR SIZE FILES DIRS
WOOmFwZfQwM \\?\c:\Go /go-backup Running Synced NO 268.53 MB 7306 961
### Backups
eg.email@example.co.nz:/$ backup c:/cmake /cmake-backup --period="0 0 4 * * *" --num-backups=3
Backup established: c:/cmake into /cmake-backup period="0 0 4 * * *" Number-of-Backups=3
eg.email@example.co.nz:/$ backup
TAG LOCALPATH REMOTEPARENTPATH STATUS
166 \\?\c:\cmake /cmake-backup COMPLETE
eg.email@example.co.nz:/$ backup -h
TAG LOCALPATH REMOTEPARENTPATH STATUS
166 \\?\c:\cmake /cmake-backup COMPLETE
-- HISTORY OF BACKUPS --
NAME DATE STATUS FILES FOLDERS
cmake_bk_20180426133300 26Apr2018 13:33:00 COMPLETE 0 92
### WebDAV
eg.email@example.co.nz:/$ webdav myfile.tif --port=1024
Serving via webdav myfile.tif: http://127.0.0.1:1024/5mYHQT4B/myfile.tif
eg.email@example.co.nz:/$ webdav
WEBDAV SERVED LOCATIONS:
/myfile.tif: http://127.0.0.1:1024/5mYHQT4B/myfile.tif
eg.email@example.co.nz:/$ webdav -d myfile.tif
myfile.tif no longer served via webdav
### Exporting and importing
eg.email_1@example.co.nz:/$ export -a Pictures/
MEGA respects the copyrights of others and requires that users of the MEGA cloud service comply with the laws of copyright.
You are strictly prohibited from using the MEGA cloud service to infringe copyrights.
You may not upload, download, store, share, display, stream, distribute, email, link to, transmit or otherwise make available any files, data or content that infringes any copyright or other proprietary rights of any person or entity. Do you accept this terms? (Yes/No): Yes
Please enter [y]es/[n]o/[a]ll/none:yes
Exported /Pictures: https://mega.nz/#F!iaZlEBIL!mQD3rFuJhKov0sco-6s9xg
eg.email_1@example.co.nz:/$ export
Pictures (folder, shared as exported permanent folder link: https://mega.nz/#F!iaZlEBIL!mQD3rFuJhKov0sco-6s9xg)
eg.email_1@example.co.nz:/$ logout --keep-session
Logging out...
Session closed but not deleted. Warning: it will be restored the next time you execute the application. Execute "logout" to delete the session permanently.
You can also login with the session id: ARo7aiLAxK-jseOdVBYhj285Twb06ivWsFmT4XAnkTsiaDRRbm5oYS1zRm-V3I0FHHOvwj7P2RPvrSw_
MEGA CMD> login eg.email_2@example.co.nz
Password:
[SDK:info: 01:55:04] Fetching nodes ...
[SDK:info: 01:55:05] Loading transfers from local cache
[SDK:info: 01:55:05] Login complete as eg.email_2@example.co.nz
eg.email_2@example.co.nz:/$ ls
Welcome to MEGA.pdf
eg.email_2@example.co.nz:/$ import https://mega.nz/#F!iaZlEBIL!mQD3rFuJhKov0sco-6s9xg
Imported folder complete: /Pictures
eg.email_2@example.co.nz:/$ ls
Pictures
Welcome to MEGA.pdf
eg.email_2@example.co.nz:/$ ls Pictures/
Camera Roll
Feedback
Saved Pictures
megacmdpkg.gif
megacmdpkg_80.gif
megacmdpkg_gray.gif
eg.email_2@example.co.nz:/$ logout
Logging out...
MEGA CMD> login ARo7aiLAxK-jseOdVBYhj285Twb06ivWsFmT4XAnkTsiaDRRbm5oYS1zRm-V3I0FHHOvwj7P2RPvrSw_
eg.email_1@example.co.nz:/$ export
Pictures (folder, shared as exported permanent folder link: https://mega.nz/#F!iaZlEBIL!mQD3rFuJhKov0sco-6s9xg)
eg.email_1@example.co.nz:/$ export -d Pictures/
Disabled export: /Pictures
eg.email_1@example.co.nz:/$ export
Couldn't find anything exported below current folder. Use -a to export it
### Transfers
eg.email@example.co.nz:/tmp-test/Mega.dir$ transfers
DIR/SYNC TAG SOURCEPATH DESTINYPATH PROGRESS STATE
U 17361 \\?\C:\Users\ME\...ebug\megaapi.obj /tmp-test/Mega.dir/Mega.dir/Debug 100.00% of 2016.62 KB ACTIVE
U 17362 \\?\C:\Users\ME\...megaapi_impl.obj /tmp-test/Mega.dir/Mega.dir/Debug 13.64% of 13.85 MB ACTIVE
U 17363 \\?\C:\Users\ME\...g\megaclient.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 15.46 MB QUEUED
U 17364 \\?\C:\Users\ME\..._http_parser.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 85.15 KB QUEUED
U 17365 \\?\C:\Users\ME\...ega_utf8proc.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 312.44 KB QUEUED
U 17366 \\?\C:\Users\ME\...\mega_zxcvbn.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 589.88 KB QUEUED
U 17367 \\?\C:\Users\ME\...ir\Debug\net.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 3.20 MB QUEUED
U 17368 \\?\C:\Users\ME\...r\Debug\node.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 3.73 MB QUEUED
U 17369 \\?\C:\Users\ME\...ntactrequest.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 352.22 KB QUEUED
U 17370 \\?\C:\Users\ME\...\Debug\proxy.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 203.57 KB QUEUED
... Showing first 10 transfers ...
eg.email@example.co.nz:/tmp-test/Mega.dir$ transfers -p 17367
Transfer 17367 paused successfully.
eg.email@example.co.nz:/tmp-test/Mega.dir$ transfers -c 17370
Transfer 17370 cancelled successfully.
eg.email@example.co.nz:/tmp-test/Mega.dir$ transfers
DIR/SYNC TAG SOURCEPATH DESTINYPATH PROGRESS STATE
U 17362 \\?\C:\Users\ME\...megaapi_impl.obj /tmp-test/Mega.dir/Mega.dir/Debug 96.32% of 13.85 MB ACTIVE
U 17363 \\?\C:\Users\ME\...g\megaclient.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.20% of 15.46 MB ACTIVE
U 17364 \\?\C:\Users\ME\..._http_parser.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 85.15 KB QUEUED
U 17365 \\?\C:\Users\ME\...ega_utf8proc.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 312.44 KB QUEUED
U 17366 \\?\C:\Users\ME\...\mega_zxcvbn.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 589.88 KB QUEUED
U 17367 \\?\C:\Users\ME\...ir\Debug\net.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 3.20 MB PAUSED
U 17368 \\?\C:\Users\ME\...r\Debug\node.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 3.73 MB QUEUED
U 17369 \\?\C:\Users\ME\...ntactrequest.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 352.22 KB QUEUED
U 17371 \\?\C:\Users\ME\...pubkeyaction.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 355.75 KB QUEUED
U 17372 \\?\C:\Users\ME\...ebug\request.obj /tmp-test/Mega.dir/Mega.dir/Debug 0.00% of 933.14 KB QUEUED
... Showing first 10 transfers ...
### Shared folders
eg.email@example.co.nz:/$ mount
ROOT on /
INBOX on //in
RUBBISH on //bin
INSHARE on //from/family.member@example.co.nz:photos_Jan_1_2020 (read access)
INSHARE on //from/family.member@example.co.nz:other_folder (read access)
eg.email@example.co.nz:/$ ls family.member@example.co.nz:photos_Jan_1_2020
photo1.jpg
photo2.jpg
eg.email@example.co.nz:/$ get family.member@example.co.nz:photos_Jan_1_2020/photo1.jpg
TRANSFERRING ||###########################################################################################||(5/5 MB: 100.00 %)
Download finished: .\photo1.jpg
eg.email@example.co.nz:/$ share -a --with=family.member@example.co.nz --level=0 "/Camera Uploads/my_photos_from_that_day"
Shared /Camera Uploads/my_photos_from_that_day : family.member@example.co.nz accessLevel=0