Rust
Rust
Rename or Move a Remote FTP File
See more FTP Examples
Demonstrates the Chilkat Ftp2.RenameRemoteFile method, which renames or moves a remote file or directory using the FTP RNFR/RNTO sequence. The first argument is the existing path and the second is the new path.
Background: Rename and move are the same
RNFR/RNTO operation: changing only the final path component renames in place, while including directory components in the new path relocates the item within the same server. It is a metadata operation, so even a large file moves instantly — but both paths must be on the same server, and moving onto an existing target may fail depending on the server.Chilkat Rust Downloads
// Demonstrates the Ftp2.RenameRemoteFile method, which renames or moves a remote file or
// directory using the FTP RNFR/RNTO sequence. The 1st argument is the existing path and the 2nd
// is the new path.
let ftp = chilkat::Ftp2::new();
ftp.set_hostname("ftp.example.com");
ftp.set_username("myFtpLogin");
// Normally you would not hard-code the password in source. You should instead obtain it
// from an interactive prompt, environment variable, or a secrets vault.
ftp.set_password("myPassword");
if ftp.connect().is_err() {
println!("{}", ftp.last_error_text());
return;
}
if ftp.change_remote_dir("public_html").is_err() {
println!("{}", ftp.last_error_text());
return;
}
// Rename a file in place.
if ftp.rename_remote_file("report.pdf", "report_final.pdf").is_err() {
println!("{}", ftp.last_error_text());
return;
}
// Include directory components in the new path to move the item within the same server.
if ftp.rename_remote_file("report_final.pdf", "archive/report_final.pdf").is_err() {
println!("{}", ftp.last_error_text());
return;
}
println!("Renamed and moved.");
if ftp.disconnect().is_err() {
println!("{}", ftp.last_error_text());
return;
}