Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gvfs(7) [centos man page]

GVFS(7) 						   Conventions and miscellaneous						   GVFS(7)

NAME

       gvfs - GIO virtual file system

DESCRIPTION

       GIO provides a VFS API to GLib applications. It includes a 'local' implementation using POSIX. gvfs provides implementations that go beyond
       that and allow to access files and storage using many protocols, such as ftp, http, sftp, dav, obexftp, etc. It also provides support for
       trash folders, for cd burning and for monitoring interesting devices and volumes on the computer.

       Applications use gvfs indirectly, by means of GIO loading the gvfs module that implements the GIO extension points. The gvfs support for
       volume monitoring is included in a separate loadable module.

       The actual gvfs implementation is distributed over a number of processes. None of these are expected to be started from the commandline,
       except for debugging purposes.

       Main processes:

       o   gvfsd - the main gvfs daemon

       o   gvfs-fuse-daemon - mounts gvfs as a fuse filesystem

       o   gvfsd-metadata - writes gvfs metadata

       Volume monitors:

       o   gvfs-udisks2-volume-monitor - a udisks-based volume monitor

       o   gvfs-afc-volume-monitor - a volume monitor for Apple iPhone/iPod Touch devices

       Mount backends:

       o   gvfsd-afc - mounts iPhone/iPod touch volumes

       o   gvfsd-afp - mounts Apple Filing Protocol volumes

       o   gvfsd-afp-browse - browses Apple Filing Protocol volumes

       o   gvfsd-archive - mounts archive files in various formats

       o   gvfsd-burn - provides a location for burning CDs

       o   gvfsd-cdda - mounts audio CDs

       o   gvfsd-computer - provides computer://

       o   gvfsd-dav - mounts DAV filesystems

       o   gvfsd-dnssd - browses dnssd

       o   gvfsd-ftp - mounts over FTP

       o   gvfsd-http - mounts over HTTP

       o   gvfsd-localtest - a test backend

       o   gvfsd-network - provides network://

       o   gvfsd-obexftp - mounts over obexftp

       o   gvfsd-recent - provides recent://

       o   gvfsd-sftp - mounts over sftp

       o   gvfsd-smb - mounts Windows Shares Filesystem volumes

       o   gvfsd-smb-browse - browses Windows Shares Filesystem volumes

       o   gvfsd-trash - provides trash://

ENVIRONMENT

       GIO_USE_VFS
	   If set, specifies the GIO vfs implementation to use. Possible values include 'local' and 'gvfs'.

       GIO_USE_VOLUME_MONITOR
	   If set, specifies the GIO volume monitor implementation to use. Possible values include 'unix', 'GProxyVolumeMonitorUDisks2', as well
	   as other native volume monitors that are described in the key files in $XDG_DATA_DIRS/gvfs/remote-volume-monitors.

FILES

       $XDG_DATA_DIRS/gvfs/mounts
	   This directory contains key files describing mount daemons.

       $XDG_DATA_DIRS/gvfs/remote-volume-monitors
	   This directory contains key files describing remote volume monitors.

SEE ALSO

       GIO documentation[1], gvfsd(1), gvfsd-fuse(1), gvfsd-metadata(1)

NOTES

	1. GIO documentation
	   http://developer.gnome.org/gio

gvfs																	   GVFS(7)

Check Out this Related Man Page

lvmpvg(4)						     Kernel Interfaces Manual							 lvmpvg(4)

NAME

       lvmpvg - LVM physical volume group information file

SYNOPSIS

DESCRIPTION

       is  an  ASCII file that stores the volume-group information for all of the physical volume groups in the system.  The information is stored
       in a hierarchical format.

       First, it starts with a volume group under which multiple physical volume groups can exist.  Under each physical volume group,  a  list	of
       physical  volumes  can be specified.  There must be at least one physical volume group in each volume group that appears in this file.  The
       physical-volume-group name must be unique within the corresponding volume group, although it is permissible to use a common physical volume
       group name across different volume groups.  There can be as many volume groups in this file as there are in the system.

       Instead of using the and commands, the administrator can edit this file to create and extend physical volume groups.  However, care must be
       taken to ensure that all physical volumes to be included in the file have already been defined in their respective volume groups by  previ-
       ous use of or

       The  file  format  has  the  following structure.  and are keywords that introduce the names of the volume group and physical volume group,
       respectively.

	      pv_path
		 ...
	      pv_path
		 ...
	      pv_path
		 ...

       The variables are defined as follows:

	      pv_path	     The block device path name of a physical volume within the volume group.

	      pvg_name	     The name of the physical volume group.  It must be unique within the volume group.

	      vg_name	     The path name of the volume group.

EXAMPLES

       The following example shows an file containing two volume groups: the first containing two physical volume groups, each with  two  physical
       volumes defined in it; the second containing three physical volume groups, each with one physical volume defined in it.

SEE ALSO

       vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M), intro(7), lvm(7).

																	 lvmpvg(4)
Man Page