|0.1.16||Aug 7, 2018|
|0.1.15||Jun 11, 2018|
|0.1.13||Dec 17, 2017|
|0.1.12||Nov 7, 2017|
|0.1.2||Dec 28, 2016|
#27 in Filesystem
421 downloads per month
Used in 3 crates
The interface to
symlinkat, and other functions in
Licensed under either of
- Apache License, Version 2.0, (./LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (./LICENSE-MIT or http://opensource.org/licenses/MIT) at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Main concept here is a
Dir which holds
O_PATH file descriptor, you
can create it with:
Dir::open("/some/path")-- open this directory as a file descriptor
Dir::from_raw_fd(fd)-- uses a file descriptor provided elsewhere
Note after opening file descriptors refer to same directory regardless of
where it's moved or mounted (with
mount --move). It may
also be unmounted or be out of chroot and you will still be able to
access files relative to it.
Note2: The constructor
Dir::cwd() is deprecated, and it's recommended
Most other operations are done on
Dir object and are executed relative
Functions that expect path relative to the directory accept both the
traditional path-like objects, such as Path, PathBuf and &str, and
Entry type returned from
list_dir(). The latter is faster as underlying
system call wants
CString and we keep that in entry.
Note that if path supplied to any method of dir is absolute the Dir file descriptor is ignored.
Also while all methods of dir accept any path if you want to prevent certain symlink attacks and race condition you should only use a single-component path. I.e. open one part of a chain at a time.