Ma/mscp
1
0
Fork 0
mirror of https://github.com/upa/mscp.git synced 2026-05-22 05:17:29 +08:00
Code Issues Packages Projects Releases 1 Wiki Activity

fix typo (#10)

Browse Source
This commit is contained in:
Ryo Nakamura
2024-03-12 15:30:41 +09:00
parent 0d248c5f6b
commit d03ae9f592
2 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/mscp.1.in
View File

@@ -159,8 +159,8 @@ file is passed,
reads the checkpoint to load a remote host, copy direction, and files reads the checkpoint to load a remote host, copy direction, and files
and their chunks to be transferred. Namely, and their chunks to be transferred. Namely,
.B mscp .B mscp
can resume a past failed transfer from the checkpoint. Resumeing with can resume a past failed transfer from the checkpoint. Resuming with a
a checkpoint does not require checkpoint does not require
.I source ... target .I source ... target
arguments. Other SSH connection options, such as port number and arguments. Other SSH connection options, such as port number and
config file, should be specified as with the failed run. In addition, config file, should be specified as with the failed run. In addition,
@@ -168,7 +168,7 @@ checkpoint files have file paths as relative paths. Thus, you must run
.B mscp .B mscp
in the same working directory as the failed run. You can see the in the same working directory as the failed run. You can see the
contents of a checkpoint file with the contents of a checkpoint file with the
.B mscp \-vv \-D \-R CHECKOPOINT .B mscp \-vv \-D \-R CHECKPOINT
command (Dry-run mode). Note that the checkpoint file is not command (Dry-run mode). Note that the checkpoint file is not
automatically removed after the resumed transfer ends automatically removed after the resumed transfer ends
successfully. Users should check the return value of successfully. Users should check the return value of
@@ -358,7 +358,7 @@ Save a checkpoint if transfer fails:
.fi .fi
.PP .PP
Check the remaining files and chunkes, and resume the failed transfer: Check the remaining files and chunks, and resume the failed transfer:
.nf .nf
# Dump the content of a checkpoint and exit (dry-run mode) # Dump the content of a checkpoint and exit (dry-run mode)
@@ -403,9 +403,9 @@ DOI
.UE . .UE .
.SH CONTACT INFROMATION .SH CONTACT INFORMATION
.PP .PP
For pathces, bug reports, or feature requests, please open an issue on For patches, bug reports, or feature requests, please open an issue on
.UR https://\:github\:.com/\:upa/\:mscp .UR https://\:github\:.com/\:upa/\:mscp
GitHub GitHub
.UE . .UE .

14
doc/mscp.rst
View File

@@ -2,7 +2,7 @@
MSCP MSCP
==== ====
:Date: v0.1.4-25-gf3a24e0 :Date: v0.1.4-28-g0d248c5
NAME NAME
==== ====
@@ -82,14 +82,14 @@ OPTIONS
file is passed, **mscp** reads the checkpoint to load a remote host, file is passed, **mscp** reads the checkpoint to load a remote host,
copy direction, and files and their chunks to be transferred. Namely, copy direction, and files and their chunks to be transferred. Namely,
**mscp** can resume a past failed transfer from the checkpoint. **mscp** can resume a past failed transfer from the checkpoint.
Resumeing with a checkpoint does not require *source ... target* Resuming with a checkpoint does not require *source ... target*
arguments. Other SSH connection options, such as port number and arguments. Other SSH connection options, such as port number and
config file, should be specified as with the failed run. In addition, config file, should be specified as with the failed run. In addition,
checkpoint files have file paths as relative paths. Thus, you must checkpoint files have file paths as relative paths. Thus, you must
run **mscp** in the same working directory as the failed run. You can run **mscp** in the same working directory as the failed run. You can
see the contents of a checkpoint file with the **mscp -vv -D -R see the contents of a checkpoint file with the **mscp -vv -D -R
CHECKOPOINT** command (Dry-run mode). Note that the checkpoint file CHECKPOINT** command (Dry-run mode). Note that the checkpoint file is
is not automatically removed after the resumed transfer ends not automatically removed after the resumed transfer ends
successfully. Users should check the return value of **mscp** and successfully. Users should check the return value of **mscp** and
remove the checkpoint if it returns 0. remove the checkpoint if it returns 0.
@@ -229,7 +229,7 @@ Save a checkpoint if transfer fails:
$ mscp -W mscp.checkpoint many-large-files 10.0.0.1:dst/ $ mscp -W mscp.checkpoint many-large-files 10.0.0.1:dst/
Check the remaining files and chunkes, and resume the failed transfer: Check the remaining files and chunks, and resume the failed transfer:
:: ::
@@ -264,10 +264,10 @@ File Transfer over SSH. In Practice and Experience in Advanced Research
Computing (PEARC '23). Association for Computing Machinery, New York, Computing (PEARC '23). Association for Computing Machinery, New York,
NY, USA, 320–323. `DOI <https://doi.org/10.1145/3569951.3597582>`__. NY, USA, 320–323. `DOI <https://doi.org/10.1145/3569951.3597582>`__.
CONTACT INFROMATION CONTACT INFORMATION
=================== ===================
For pathces, bug reports, or feature requests, please open an issue on For patches, bug reports, or feature requests, please open an issue on
`GitHub <https://github.com/upa/mscp>`__. `GitHub <https://github.com/upa/mscp>`__.
AUTHORS AUTHORS