At line 3 changed one line |
A leading "L" character instructs the client to apply the command to the local client versus to the remote client. lls would sit your current local folder, lcd changes the local folder. Only the file transfer commands do not have an "L" version. (put, get, diffput, diffget) If a path being references has a space in it, the path must be quoted. Example: put "some file.txt" "/some folder/my file.txt". Backslash quote escaping is permitted as well. The "local" client doesn't need to be local at all though, both clients can be remote and files can be streamed through the CrushClient. |
A leading "L" character instructs the client to apply the command to the local client versus to the remote client. lls would sit your current local folder, lcd changes the local folder. Only the file transfer commands do not have an "L" version. (put, get, diffput, diffget) If a path being referenced has a space in it, the path must be quoted. Example: put "some file.txt" "/some folder/my file.txt". Backslash quote escaping is permitted as well. The "local" client doesn't need to be local at all though, both clients can be remote and files can be streamed through the CrushClient. Commands can be sent into he background with a "&" at the end of them. Example: |
{{{ |
put file.txt remote.txt& |
}}} |
At line 6 changed one line |
Different ways to start CrushClient. If started with a script, no input will be taken, all input will be read line by line from the script as if you were physically typing it. Don't forget the quit command at the end or the client will wait indefinitely for more input... A script is typically ended with two lines. wait, then quit. |
There are different ways to start CrushClient. If started with a script, no input will be taken, all input will be read line by line from the script as if you were physically typing it. Don't forget the quit command at the end or the client will wait indefinitely for more input... A script is typically ended with two lines. wait, then quit. |
At line 15 added one line |
java -jar CrushTunnel.jar inline_script "connect https://demo:demo@crushftp.com/demo/;put file.txt;wait;quit;" |
At line 19 added 3 lines |
---- |
!!Commands |
|
At line 136 changed one line |
Example: set download_threads 10 |
Example: set max_threads 10 |
At line 170 changed 2 lines |
info |
linfo |
info [all/clear] |
linfo [all/clear] |
At line 185 added 39 lines |
---- |
Kill app after pre-determined time amount with an error code exit. |
{{{ |
kill 30 secs |
kill 30 s |
kill 1 min |
kill 1 m |
kill 100 hours |
kill 100 h |
kill 2 days |
kill 2 d |
kill 0 s (aborts kill) |
}}} |
---- |
Timeout on individual file transfer items FTP, HTTP(s), SFTP in seconds. |
{{{ |
timeout 30 |
}}} |
---- |
Start a tunnel with a server so you can connect through it. After starting you can connect through the tunnels port. Typically its 55555. |
{{{ |
tunnel https://www.crushftp.com/ (you will be prompted for credentials) |
tunnel https://demo:demo@www.crushftp.com/ (credentials provided inline in the URL) |
tunnel list (list running and stopped tunnels) |
tunnel stop {id} (stop a tunnel id you got from the list command, ids start at 1 and count up for each tunnel you create. Once stopped, a tunnel id can't be started.) |
tunnel log (prints out the recent tunnel log messages) |
|
connect http://127.0.0.1:55555/ (now you can connect normally through the tunnel that was just started) |
}}} |
---- |
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 |
}}} |