NAME
smd-push - syncs the remote mail dir letting the local one untouched
SYNOPSIS
smd-push [-v|--verbose] [-t|--template-only] [endpoint]
DESCRIPTION
smd-push performs in the remote maildir all the changes that were
performed on the local one.
No changes are made on the local maildir. Use smd-pull(1) for that.
The first time this program is run a new config file is created and the
user is asked to edit it. That file is composed by the following fields
CLIENTNAME
name of the client host
SERVERNAME
name of the server host MAILBOX A list of directories, separated
by space
The field SERVERNAME must be a valid name for ssh, thus can be an alias
like
smd-server-foo.
The default config file contains an example of how to set up an
alias for ssh.
The field CLIENTNAME is just an ID for the local host. If you plan to
sync the same host with multiple remote hosts, you MUST use different
values for CLIENTNAME for every configuration file.
The config file is a regular shell script, refer to bash(1) for its
syntax.
The content of the directories ~/.smd/hooks/{pre,post}-push.d/ is
executed respectively before and after smd-push does it’s job. They
receive four arguments: "pre" or "post", "push", the endpoint name and
the status. The status is always 0 (meaning success) for pre hooks,
while can be 1 (for failure) for post hooks. Hooks should not fail, if
they do so then smd-push will fail too.
OPTIONS
-v --verbose
Verbose, machine-readable, output
-t --template-only
Just create a template configuration file if none
endpoint
Is the suffix for the name of the configuration file to use. If
it is omitted, the configuration file ~/.smd/config.default is
used.
FILES
~/.smd/config.* ~/.smd/hooks/pre-push.d/ ~/.smd/hooks/post-push.d/
SEE ALSO
mddiff(1), smd-server(1), smd-client(1), smd-pull(1), smd-loop(1)
AUTHOR
Enrico Tassi <gares@fettunta.org>
20 June 2010 smd-push(1)