Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

PERFUSED(8)		  BSD System Manager's Manual		   PERFUSED(8)

NAME
     perfused — PUFFS Enabled Relay to FUSE Daemon

SYNOPSIS
     perfused [-fs] [-d types] [-i -fd]

DESCRIPTION
     perfused is a userland daemon implementing the FUSE kernel level API.  It
     creates a /dev/fuse socket for FUSE file system daemons to connect to.
     perfused takes care of mounting the file system using puffs(3).

     When the kernel sends a puffs(3) operation for the mounted file system,
     perfused will translate it into a FUSE request, and will send it to the
     file system daemon through /dev/fuse.  The FUSE reply will be converted
     back into a puffs(3) reply and will be relayed to the kernel.

     FUSE file system daemons must be modified so that they request perfused
     to perform the mount(2) system call instead of doing it on their own.
     This is done by replacing mount(2) and the open(2) calls for /dev/fuse
     with perfuse_mount() and perfuse_open(), respectively, in their sources.
     libperfuse(3) must be used at link time.  Most FUSE file system daemons
     use libfuse and will work unmodified, provided the modification is done
     in libfuse itself .

     The following options are available:

     -d types	 Print additional debug information.  types is a comma-sepa‐
		 rated list of information types to print:

		 puffs	 Display PUFFS requests and replies.

		 fuse	 Display FUSE requests and replies.

		 dump	 Dump content of FUSE frames.

		 fh	 Display file handle activity.

		 reclaim
			 Display reclaim activity.

		 readdir
			 Display readdir activity.

		 requeue
			 Display requeue activity.

		 sync	 Display dirty flags and sync operations.

     -f		 Do not fork, but stay in the foreground.

     -i fd	 Do not open /dev/fuse but use the socket available from the
		 file descriptor fd.  This is used when perfused is started
		 from libperfuse(3).

     -s		 Enable debug output only when receiving SIGINFO.

SIGNALS
     SIGINFO
	     If the -s flag was used, toggle debug output.  Do nothing other‐
	     wise.

     SIGUSR1
	     Toggle FUSE operation dump on and off.  When toggling off, the
	     trace is is stored in /var/run/perfuse-xxx.trace (xxx is the
	     filesystem mount point).

ERRORS
     The program logs to the syslog daemon as facility “daemon”.  For detailed
     debugging use the -d (debug) option.

SEE ALSO
     mount(2), perfuse_mount(3), puffs(4)

AUTHORS
     The program was written by Emmanuel Dreyfus ⟨manu@NetBSD.org⟩.

BUGS
     When perfused runs in the foreground (using the -f flag), some processes
     using the FUSE file system will sometime hang on ‘uvn_fp2’.

BSD			       January 29, 2012				   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome