Third-partyĭevelopers create innovative backup, restore, GUI and business process
Rclone is widely used on Linux, Windows and Mac. Official Ubuntu, Debian, Fedora, Brew andĬhocolatey repos.
Rclone is mature, open-source software originally inspired by Local, cloud or virtual filesystem as a disk on Windows, macOS, linux and Virtual backends wrap local and cloud file systems to apply Where possible, rclone employs server-side transfers to minimise localīandwidth use and transfers from one provider to another without using local Intermittent connections, or subject to quota can be restarted, from the Users call rclone "The Swiss army knife of cloud storage", and "Technology indistinguishable from magic". Includes shell pipeline support, and -dry-run protection. Rclone has powerful cloud equivalents to the unix commands rsync,Ĭp, mv, mount, ls, ncdu, tree, rm, and cat. Over 40 cloud storage products support rclone including S3 object stores,īusiness & consumer file storage services, as well as standard transfer It is a feature-rich alternative to cloud vendors' web storage interfaces. Rclone is a command-line program to manage files on cloud storage. Hopefully everyone else is smart enough to do this the right way the first time, but figured I’d post this incase some other poor sysadmin is having the same confusion over the invalid character message.Rclone syncs your files to cloud storage This will work happily on all versions since it’s correct syntax of the command line options. The correct solution, is to always have the target user as the final field, after the command line options, aka: # mail -s " message" root s SUBJECT -a FILE -q FILE -f FILE -A ACCOUNT -b USERS -c USERS \ Usage: mail -eiIUdEFntBDNHRV~ -T FILE -u USER -h hops -r address \ Viewing the help on both versions shows that options need to come before the destination user, however it seems that older versions of mailx were a bit slacker and accepted some flexibility of command line options. Turns out that between mailx version 8.1.1 and mailx version 12.4, the mailx binary got a lot more fussy about the formatting of the command line options. What I found is that on CentOS/RHEL 5, the following would work fine: # mail root -s " message"īut on CentOS/RHEL 6, it would ignore the subject field (as can be seen by it re-asking for it) and then fail with an annoying “invalid character” error: # mail root -s " message" One problem I encountered was a number of scripts failing when sending emails, throwing out messages to STDERR: contains invalid character '[' Whilst my network is predominately CentOS 5 hosts, I’ve started moving many of them to CentOS 6, mostly on a basis of doing so whenever a host needs a particularly newer version, since I don’t really want to spend an entire week rebuilding all 30-odd VMs.