Hi,
I am currently using mscp-0.2.1 for some data transfers and noticed some behavior that I was wondering on how to resolve it easily.
We run transfers using a command similar to:
mscp '/THIS/IS/AN/EXAMPLE/PATH/' USER@IP:/THIS/IS/ANOTHER/EXAMPLE/PATH/
The issue appears when a transfer crashes or gets interrupted and we restart it the same command. Instead of overwriting or continuing into the existing destination directory, mscp creates a new nested directory because the target directory already exists.
As an example, after rerunning the command, we observe behavior similar to:
/THIS/IS/ANOTHER/EXAMPLE/PATH/PATH/
instead of continuing the transfer into the existing directory structure, more comparable to how rsync behaves.
I assume this is expected default scp/mscp behaviour, but I was wondering if there is a way to mimic rsync-like behaviour when resuming transfers without using checkpointing, so just overwriting the existing files and redoing the entire transfer. Is this resolved in #24 ? Or does that relate to a different issue with creating nested dirs in general.
Kind regards,
Serge
Hi,
I am currently using mscp-0.2.1 for some data transfers and noticed some behavior that I was wondering on how to resolve it easily.
We run transfers using a command similar to:
mscp '/THIS/IS/AN/EXAMPLE/PATH/' USER@IP:/THIS/IS/ANOTHER/EXAMPLE/PATH/The issue appears when a transfer crashes or gets interrupted and we restart it the same command. Instead of overwriting or continuing into the existing destination directory, mscp creates a new nested directory because the target directory already exists.
As an example, after rerunning the command, we observe behavior similar to:
/THIS/IS/ANOTHER/EXAMPLE/PATH/PATH/instead of continuing the transfer into the existing directory structure, more comparable to how rsync behaves.
I assume this is expected default scp/mscp behaviour, but I was wondering if there is a way to mimic rsync-like behaviour when resuming transfers without using checkpointing, so just overwriting the existing files and redoing the entire transfer. Is this resolved in #24 ? Or does that relate to a different issue with creating nested dirs in general.
Kind regards,
Serge