Function set_permissions_nofollow 

pub fn set_permissions_nofollow<P: AsRef<Path>>(
    path: P,
    perm: Permissions,
) -> Result<()>

🔬This is a nightly-only experimental API. (set_permissions_nofollow #141607)

Changes the permissions found on a file or a directory. On certain platforms, if the file is a symlink, it will change the permissions bits on the symlink itself rather than the target (e.g. Windows, BSD, MacOS). On other platforms, this results in an error when attempting to change permissions on a symlink (e.g. Linux).

Note that non-final path elements are allowed to be symlinks.

Platform-specific behavior

This function currently corresponds to:

• open with O_NOFOLLOW flag enabled + fchmod on WASI
• fchmodat function with the flag AT_SYMLINK_NOFOLLOW enabled on Unix platforms
• The flag FILE_FLAG_OPEN_REPARSE_POINT is enabled and then the permissions of the file is set through SetFileInformationByHandle on Windows.
• On all other platforms, the behavior remains the same with fs::set_permissions.

Note that, this may change in the future.

Errors

This function will return an error in the following situations, but is not limited to just these cases:

• path does not exist.
• The user lacks the permission to change attributes of the file.

Note: On Linux, this will result in a Unsupported error if the final element is a symlink. On BSD-based systems, the behavior can vary from symlink permission bits changing or there being no effects on symlinks

Examples

#![feature(set_permissions_nofollow)]
use std::fs;

fn main() -> std::io::Result<()> {
    let mut perms = fs::symlink_metadata("foo.txt")?.permissions();
    perms.set_readonly(true);
    // This should result in an error on certain platforms
    // or succeed in modifying the permissions of a symlink
    fs::set_permissions_nofollow("foo.txt", perms)?;
    Ok(())
}