ZXPUSH(1): push changes for a replica
__________________________________________________
USAGE
usage: zxpush [-Dabnuv] file
-D: debug
-a: all
-b: blind
-n: dry run
-u: don't use unix out
-v: verbose
DESCRIPTION
Zxpush pushes changes to a remote tree from a local replica. It
compares local and remote changes and decides which changes must
be pushed and which ones must be pulled. The newest change wins
if there is a conflicting change. File removes are noted and
using the modification time for their directory. If a directory
is added or removed, inner files and directories are added or
removed as well no matter if the other replica has changes for
such inner files. See zxrepl(1) for usage examples.
Flag -a pushes all the changes to the remote without paying
attention to any remote file or change made. This flag is meant
to initialize the remote file tree by making it equal to the
local replica after the replica has been created, but it can be
used at any time and will discard all remote changes in favor of
the local tree.
Flag -b does not consider remote changes when pushing and
propagates all changes made in the local tree to the remote one.
If no argument is given, zxpush pushes all replicas found at
/u/lib/repl.
When given, the file argument names the replica and the database
files. The replica is the basename for file. The local database
file is file with '.ldb' appended. The remote database file is
file with '.rdb' appended. If file does not contain '/' then
'/u/lib/repl/' is prepended to it.
Metadata changes at the root of the replica are always ignored.
SOURCE
+o /zx/sys/src/clive/cmd/zxpush
SEE ALSO
+o zxrepl(1) to create replicas.
+o zxpull(1) to pull changes.
+o zxsync(1) to synchronize changes.
__________________________________________________
User's manual. Section 1. Copyright © LSUB 2014-2016