|
Remote Commands Over SSH
Checksum Commands
Your rsync.net filesystem has access to the following checksum commands: md5, sha1, sha256 and rmd160 Remote checksums are run in this manner:
ssh 1234@usw-s001.rsync.net md5 some/file
Pipelining Through 'dd' (Database Dumps)
pg_dump -U postgres db | ssh 1234@usw-s001.rsync.net \
or perhaps:
mysqldump -u mysql db | ssh 1234@usw-s001.rsync.net \
Data Transfer to/from Amazon S3
rsync.net maintains the s3cmd binary in our environment so you can transfer data to and from Amazon S3:
ssh user@rsync.net s3cmd get s3://rsynctest/mscdex.exe
All you need to do is create a default .s3cfg file in the root of your rsync.net filesystem (you need to place this there manually, as --configure is disabled) and then edit the access_key and secret_key fields. After you edit those two fields, you can begin running s3cmd commands remotely, like this:
ssh user@rsync.net s3cmd ls s3://rsynctest
A copy of the default .s3cfg file can be found here.
git
You can run the git command in our environment to do things like this:
ssh user@rsync.net "git clone git://github.com/freebsd/freebsd.git freebsd"
Miscellaneous Unix Commands
The other remote commands that can be used over ssh are:
echo test tree tail cp (GNU) ls mkdir pwd chmod ln mv rm rmdir touch chgrp groups id s3cmd passwd quota For example, you can run something like:
ssh 1234@usw-s001.rsync.net touch some/fileand then:
ssh 1234@usw-s001.rsync.net rm -rf some/other/fileThe 'passwd' command is special, as it requires a '-t'
ssh -t 1234@usw-s001.rsync.net passwdYou can use the test command remotely, and return true/false to your local environment:
# ssh user@rsync.net "test -f fileThatExists"
|