Content-type: text/html; charset=UTF-8
void endfsent(void);
struct fstab *getfsent(void);
struct fstab *getfsfile(const char *mount_point);
struct fstab *getfsspec(const char *special_file);
struct fstab { char *fs_spec; /* block device name */ char *fs_file; /* mount point */ char *fs_vfstype; /* file-system type */ char *fs_mntops; /* mount options */ const char *fs_type; /* rw/rq/ro/sw/xx option */ int fs_freq; /* dump frequency, in days */ int fs_passno; /* pass number on parallel dump */ };
Here the field fs_type contains (on a *BSD system) one of the five strings "rw", "rq", "ro", "sw", "xx" (read-write, read-write with quota, read-only, swap, ignore).
The function setfsent() opens the file when required and positions it at the first line.
The function getfsent() parses the next line from the file. (After opening it when required.)
The function endfsent() closes the file when required.
The function getfsspec() searches the file from the start and returns the first entry found for which the fs_spec field matches the special_file argument.
The function getfsfile() searches the file from the start and returns the first entry found for which the fs_file field matches the mount_point argument.
Interface | Attribute | Value |
endfsent(),
setfsent() | Thread safety | MT-Unsafe race:fsent |
getfsent(),
getfsspec(), getfsfile() | Thread safety | MT-Unsafe race:fsent locale |
Since Linux allows mounting a block special device in several places, and since several devices can have the same mount point, where the last device with a given mount point is the interesting one, while getfsfile() and getfsspec() only return the first occurrence, these two functions are not suitable for use under Linux.