SyncEvolution 1.5 Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncxmlrpc.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncsqlite.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncqtcontacts.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncmaemocal.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/synckcalextended.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncfile.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncecal.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncebook.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncdav.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/syncactivesync.so Loading backend library /usr/lib/x86_64-linux-gnu/syncevolution/backends/platformgnome.so

List and manipulate databases: syncevolution --print-databases|--create-database|--remove-database [<properties>] [<config> <store>] Show information about configuration(s): syncevolution --print-servers|--print-configs|--print-peers Show information about a specific configuration: syncevolution --print-config [--quiet] [--] <config> [main|<store> ...] List sessions: syncevolution --print-sessions [--quiet] [--] <config> Show information about SyncEvolution: syncevolution --help|-h|--version Run a synchronization as configured: syncevolution <config> [<store> ...] Run a synchronization with properties changed just for this run: syncevolution --run <options for run> [--] <config> [<store> ...] Restore data from the automatic backups: syncevolution --restore <session directory> --before|--after [--dry-run] [--] <config> <store> ... Create, update or remove a configuration: syncevolution --configure <options> [--] <config> [<store> ...] syncevolution --remove|--migrate <options> [--] <config> List items: syncevolution --print-items [--] [<config> [<store>]] Export item(s): syncevolution [--delimiter <string>] --export <dir>|<file>|- [--] [<config> [<store> [<luid> ...]]] --luids <luid> ... Add item(s): syncevolution [--delimiter <string>|none] --import <dir>|<file>|- [--] [<config> [<store>]] --luids <luid> ... Update item(s): syncevolution --update <dir> [--] <config> <store> syncevolution [--delimiter <string>|none] --update <file>|- [--] <config> <store> <luid> ... --luids <luid> ... Remove item(s): syncevolution --delete-items [--] <config> <store> (<luid> ... | '*') Options: --sync|-s <mode>|? Temporarily synchronize the active datastores in that mode. Useful for a `refresh-from-local` or `refresh-from-remote` sync which clears all data at one end and copies all items from the other. **Warning:** `local` is the data accessed via the sync config directly and `remote` is the data on the peer, regardless where the data is actually stored physically. --print-servers|--print-configs|--print-peers Prints the names of all configured peers to stdout. There is no difference between these options, the are just aliases. --print-servers|--print-configs|--print-peers|-p Prints the complete configuration for the selected <config> to stdout, including up-to-date comments for all properties. The format is the normal .ini format with datastore configurations in different sections introduced with [<store>] lines. Can be combined with --sync-property and --datastore-property to modify the configuration on-the-fly. When one or more datastores are listed after the <config> name on the command line, then only the configs of those datastores are printed. `main` selects the main configuration instead of datastore configurations. Using --quiet suppresses the comments for each property. When setting a --template, then the reference configuration for that peer is printed instead of an existing configuration. --print-sessions Prints information about previous synchronization sessions for the selected peer or context are printed. This depends on the ``logdir`` property. The information includes the log directory name (useful for --restore) and the synchronization report. In combination with --quiet, only the paths are listed. --configure|-c Modify the configuration files for the selected peer and/or datastores. If no such configuration exists, then a new one is created using one of the template configurations (see --template option). Choosing a template sets most of the relevant properties for the peer and the default set of datastores (see above for a list of those). Anything specific to the user (like username/password) still has to be set manually. When creating a new configuration and listing datastores explicitly on the command line, only those datastores will be set to active in the new configuration, i.e. `syncevolution -c memotoo addressbook` followed by `syncevolution memotoo` will only synchronize the address book. The other datastores are created in a disabled state. When modifying an existing configuration and datastores are specified, then the datastore properties of only those datastores are modified. By default, creating a config requires a template. Datastore names on the command line must match those in the template. This allows catching typos in the peer and datastore names. But it also prevents some advanced use cases. Therefore it is possible to disable these checks in two ways: - use `--template none` or - specify all required sync and datastore properties that are normally in the templates on the command line (syncURL, backend, ...) --run|-r To prevent accidental sync runs when a configuration change was intended, but the `--configure` option was not used, `--run` must be specified explicitly when sync or datastore properties are selected on the command line and they are meant to be used during a sync session triggered by the invocation. --migrate In older SyncEvolution releases a different layout of configuration files was used. Using --migrate will automatically migrate to the new layout and rename the <config> into <config>.old to prevent accidental use of the old configuration. WARNING: old SyncEvolution releases cannot use the new configuration! The switch can also be used to migrate a configuration in the current configuration directory: this preserves all property values, discards obsolete properties and sets all comments exactly as if the configuration had been created from scratch. WARNING: custom comments in the configuration are not preserved. --migrate implies --configure and can be combined with modifying properties. --print-items Shows all existing items using one line per item using the format "<luid>[: <short description>]". Whether the description is available depends on the backend and the kind of data that it stores. --export Writes all items in the datastore or all items whose <luid> is given into a directory if the --export parameter exists and is a directory. The <luid> of each item is used as file name. Otherwise it creates a new file under that name and writes the selected items separated by the chosen delimiter string. stdout can be selected with a dash. The default delimiter (two line breaks) matches a blank line. As a special case, it also matches a blank line with DOS line ending (line break, carriage return, line break). This works for vCard 3.0 and iCalendar 2.0, which never contain blank lines. When exporting, the default delimiter will always insert two line breaks regardless whether the items contain DOS line ends. As a special case, the initial newline of a delimiter is skipped if the item already ends in a newline. --import Adds all items found in the directory or input file to the datastore. When reading from a directory, each file is treated as one item. Otherwise the input is split at the chosen delimiter. "none" as delimiter disables splitting of the input. --update Overwrites the content of existing items. When updating from a directory, the name of each file is taken as its luid. When updating from file or stdin, the number of luids given on the command line must match with the number of items in the input. --delete-items Removes the specified items from the datastore. Most backends print some progress information about this, but besides that, no further output is produced. Trying to remove an item which does not exist typically leads to an ERROR message, but is not reflected in a non-zero result of the command line invocation itself because the situation is not reported as an error by backends (removal of non-existent items is not an error in SyncML). Use a star * instead or in addition to listing individual luids to delete all items. --sync-property|-y <property>=<value>|<property>=?|? Overrides a datastore-independent configuration property for the current synchronization run or permanently when --configure is used to update the configuration. Can be used multiple times. Specifying an unused property will trigger an error message. --datastore-property|--source-property|-z <property>=<value>|<property>=?|? Same as --sync-property, but applies to the configuration of all active datastores. `--sync <mode>` is a shortcut for `--datastore-property sync=<mode>`. --template|-l <peer name>|default|?<device> Can be used to select from one of the built-in default configurations for known SyncML peers. Defaults to the <config> name, so --template only has to be specified when creating multiple different configurations for the same peer, or when using a template that is named differently than the peer. `default` is an alias for `memotoo` and can be used as the starting point for servers which do not have a built-in template. A pseudo-random device ID is generated automatically. Therefore setting the `deviceId` sync property is only necessary when manually recreating a configuration or when a more descriptive name is desired. The available templates for different known SyncML servers are listed when using a single question mark instead of template name. When using the `?<device>` format, a fuzzy search for a template that might be suitable for talking to such a device is done. The matching works best when using `<device> = <Manufacturer> <Model>`. If you don't know the manufacturer, you can just keep it as empty. The output in this mode gives the template name followed by a short description and a rating how well the template matches the device (100% is best). --status|-t The changes made to local data since the last synchronization are shown without starting a new one. This can be used to see in advance whether the local data needs to be synchronized with the server. --quiet|-q Suppresses most of the normal output during a synchronization. The log file still contains all the information. --keyring[=<value>]|-k A legacy option, now the same as setting the global keyring sync property. When not specifying a value explicitly, "true" for "use some kind of keyring" is implied. See "--sync-property keyring" for details. --daemon[=yes/no] By default, the SyncEvolution command line is executed inside the syncevo-dbus-server process. This ensures that synchronization sessions started by the command line do not conflict with sessions started via some other means (GUI, automatically). For debugging purposes or very special use cases (running a local sync against a server which executes inside the daemon) it is possible to execute the operation without the daemon (--daemon=no). --help|-h Prints usage information. --version Prints the SyncEvolution version. CONFIGURATION PROPERTIES ======================== This section lists predefined properties. Backends can add their own properties at runtime if none of the predefined properties are suitable for a certain setting. Those additional properties are not listed here. Use ``--sync/datastore-property ?`` to get an up-to-date list. The predefined properties may also be interpreted slightly differently by each backend and sync protocol. Sometimes this is documented in the comment for each property, sometimes in the documentation of the backend or sync protocol. Properties are listed together with all recognized aliases (in those cases where a property was renamed at some point), its default value, sharing state (unshared/shared/global). Some properties must be defined, which is marked with the word `required`. Sync properties --------------- << see "syncevolution --sync-property ?" >> Datastore properties -------------------- << see "syncevolution --datastore-property ?" >>