| At line 42 changed one line |
| appe will start appending the current file to the target file. |
| appe will start appending the current file to the target file.\\ |
| move will copy, then delete the source. |
| At line 48 added one line |
| move /local/file/path [remote file path] |
| At line 51 added 5 lines |
| Similar to the putdel command, but first calculates the differences between the directories and files and lists what actions it would do if you instead used putdel. It will list out the deletes and copy actions it would do to make the remote side match the local side. This command is available as of CrushClient 1.5.2 and above. |
| {{{ |
| diffdir |
| }}} |
| ---- |
| At line 182 added 16 lines |
| Forces a one way copy/replace sync operation. Anything on the destination not found on the source is deleted. Use extreme care when using this command as a single typo would mean it erases the target you specified! |
| {{{ |
| putdel /local/file/path [remote file path] |
| }}} |
| ---- |
| List the supported ciphers for HTTPS/FTPS/FTPES connections by making a test connection outbound to https://www.crushftp.com/\\ |
| Set the cipher to use for SSL/TLS connections.\\ |
| List the last used cipher for the prior connection.\\ |
| Trust all certificates, regardless if they are expired, revokes, matching, etc. Use only for debug/dev purposes, but not for real world usage!\\ |
| {{{ |
| cipher list |
| cipher set {cipher} |
| cipher get |
| cipher trust |
| }}} |
| ---- |
| At line 237 added 29 lines |
| ---- |
| Take a thread stack trace for what all CrushClient is currently working on (debug purposes only) |
| {{{ |
| dumpstack |
| }}} |
| ---- |
| Take a memory dump of the CrushClient (debug purposes only) |
| {{{ |
| dumpmemory |
| }}} |
| ---- |
| *'PUTSYNC' IS EXPERIMENTAL AND FLAWED! WARNING!\\ |
| Performs a two way sync operation. Uses the modified date on items to decide which side has the latest copy and copies in both directions. It also uses its last known run time for the sync to decide which side has the correct items and deletes items it believes were deleted from one side from the other side too! If the logic fails here, it deletes items on both sides you didn't intend for. Extreme caution should be used when considering using this command. We don't have access to any time and dates except modified times, so the logic is flawed. If you copied an item with an older date modified than the last sync time to one side, it would then get deleted as it appears as if its old...and its missing from the other side, so its not supposed to be there. Do not use this command unless you fully understand everything mentioned or you will loose data... |
| {{{ |
| putsync /local/file/path [remote file path] |
| }}} |
| ---- |
| Example script to do PGP encryption client side before uploading to a remote server (we have to turn off MD5 checking as the MD5 will no longer match if uploading to a CrushFTP server): |
| {{{ |
| set md5_check false |
| config pgpEncryptUpload true |
| config pgpPublicKeyUploadPath /mypgpkeys/customer1_key.pub |
| connect https://user:pass@someserver.domain.com/ |
| lcd /var/documents/ |
| cd / |
| put test_file.txt |
| wait |
| quit |
| }}} |
