-
Notifications
You must be signed in to change notification settings - Fork 339
Global Options
These options apply to all duplicacy commands and must be placed before any command
-verbose, -v show more detailed information
-debug, -d show even more detailed information, useful for debugging
-log enable log-style output
-stack print the stack trace when an error occurs
-no-script do not run script before or after command execution
-background read passwords, tokens, or keys only from keychain/keyring or env
-profile <address:port> enable the profiling tool and listen on the specified address:port
-comment add a comment to identify the process
-suppress, -s <id> [+] suppress logs with the specified id
-print-memory-usage print memory usage every second
-help, -h show help
duplicacy [global options] command
Show more detailed messages. For the highest level of info, choose -debug. By default, only INFO, WARNING, and ERROR messages are displayed.
Show DEBUG level messages (the highest, most detailed level of messages). By default, only INFO, WARNING, and ERROR messages are displayed.
Show the timestamp, level, and the message id of each log message.
The -stack option is used to dump the stack trace when an error occurs to help locate where the error is.
Using this option will stop Pre Command and Post Command Scripts from running. This is usually used to avoid an infinite loop of command execution.
The -background option will instruct Duplicacy not to ask for interactive password input. As a result, Duplicacy will read all credentials only from keychain/keyring or the environment variables. If a credential can't be found, an error will be reported.
This option is designed for Duplicacy GUI.
With the -profile option, you can open http://address:port/debug/pprof/ in a browser to profile a running Duplicacy instance.
Please refer to https://golang.org/pkg/net/http/pprof/ for instructions.
The -comment option was introduced to allow Duplicacy processes to be identified by arguments, for example when using ps.
Suppose you have 2 Duplicacy processes running:
duplicacy -comment LONG_OPERATION check -all &
duplicacy check -all &
when you ps ax | grep duplicacy there will be nothing of help to differentiate the 2 processes.
But when you use this option: ps ax | grep LONG_OPERATION you will find your desired process.
Do not print the log messages with the given log id. This option can be specified multiple times.
Print the memory usage every second throughout the program execution.
Show the help.