.TH "chirp_fuse" 1 "" "CCTools 7.0.9 FINAL" "Cooperative Computing Tools" .SH NAME .LP \fBchirp_fuse\fP - create a \FCFUSE\FT mount point with virtual access to remote chirp servers .SH SYNOPSIS .LP \FC\fBchirp_fuse [options] \fP\FT .SH DESCRIPTION .LP .PP You can attach to a Chirp filesystems by using the FUSE package to attach Chirp as a kernel filesystem module. Unlike \fBparrot(1)\fP, this requires superuser privileges to install the FUSE package, but will likely work more reliably on a larger number of programs and environments. Using FUSE allows for transparent access to a Chirp server via the local filesystem. This allows user applications to use a Chirp store unmodified. .PP Once you have installed and permissions to use FUSE, simply run chirp_fuse with the name of a directory on which the filesystem should be mounted. .PP For complete details with examples, see the Chirp User's Manual (\fBhttp://ccl.cse.nd.edu/software/manuals/chirp.html\fP). .SH OPTIONS .LP .LP .TP \fB-a\fP, \fB-\-auth\fP=\fI\fP . Require this authentication mode. .TP \fB-b\fP, \fB-\-block-size\fP=\fI\fP . Block size for network I/O. (default is 65536s) .TP \fB-d\fP, \fB-\-debug\fP=\fI\fP . Enable debugging for this subsystem. .TP .B \ -D, --no-optimize . Disable small file optimizations such as recursive delete. .TP .B \ -f, --foreground . Run in foreground for debugging. .TP \fB-i\fP, \fB-\-tickets\fP=\fI\fP . Comma-delimited list of tickets to use for authentication. .TP \fB-m\fP, \fB-\-mount-options\fP=\fI