getvfsent man page on SmartOS

Man page or keyword search:  
man Server   16655 pages
apropos Keyword Search (all sections)
Output format
SmartOS logo
[printable version]


       getvfsent, getvfsfile, getvfsspec, getvfsany - get vfstab file entry

       #include <stdio.h>
       #include <sys/vfstab.h>

       int getvfsent(FILE *fp, struct vfstab *vp);

       int getvfsfile(FILE *fp, struct vfstab *vp, char *file);

       int getvfsspec(FILE *, struct vfstab *vp, char *spec);

       int getvfsany(FILE *, struct vfstab *vp, struct vfstab *vref);

       The  getvfsent(), getvfsfile(), getvfsspec(), and getvfsany() functions
       each fill in the structure pointed to by vp with the broken-out	fields
       of  a  line  in	the /etc/vfstab file. Each line in the file contains a
       vfstab structure, declared in the <sys/vfstab.h> header, whose  follow‐
       ing members are described on the vfstab(4) manual page:

	      char *vfs_special;
	      char *vfs_fsckdev;
	      char *vfs_mountp;
	      char *vfs_fstype;
	      char *vfs_fsckpass;
	      char *vfs_automnt;
	      char *vfs_mntopts;

       The getvfsent() function returns a pointer to the next vfstab structure
       in the file; so successive calls can be used to search the entire file.

       The getvfsfile() function searches the file referenced by  fp  until  a
       mount  point  matching  file is found and fills vp with the fields from
       the line in the file.

       The getvfsspec() function searches the file referenced by  fp  until  a
       special device matching spec is found and fills vp with the fields from
       the line in the file.  The spec argument will try to  match  on	device
       type  (block  or character special) and major and minor device numbers.
       If it cannot match in this manner, then it compares the strings.

       The getvfsany() function searches the file referenced  by  fp  until  a
       match  is found between a line in the file and vref. A match occurrs if
       all non-null entries in vref match  the	corresponding  fields  in  the

       Note that these functions do not open, close, or rewind the file.

       If  the	next  entry  is successfully read by getvfsent() or a match is
       found with getvfsfile(), getvfsspec(), or getvfsany(), 0	 is  returned.
       If an end-of-file is encountered on reading, these functions return −1.
       If an error is encountered, a value greater than 0  is  returned.   The
       possible error values are:

		      A	 line in the file exceeded the internal buffer size of

		      A line in the file contains too many fields.

		      A line in the file contains too few fields.


       See attributes(5) for descriptions of the following attributes:

       │MT-Level       │ Safe		 │

       vfstab(4), attributes(5)

       The members of the vfstab structure point to information contained in a
       static area, so it must be copied if it is to be saved.

				 Mar 12, 1997			 GETVFSENT(3C)

List of man pages available for SmartOS

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net