Update of "Manual"
Overview

Artifact ID: 0977e1d2a002484115da23c6134513bc32e1d183
Page Name:Manual
Date: 2014-12-29 04:33:10
Original User: rkeene
Parent: 657e169f1ea74e6d2d911631774891520370196e
Content

NAME

appfsd, mount.appfs - AppFS FUSE Daemon

 

SYNOPSIS

appfsd [-dfsh] [-o option[,...]] cachedir mount_point
mount.appfs [-dfsh] [-o option[,...]] cachedir mount_point

 

DESCRIPTION

AppFS is a FUSE-based filesystem to present a manifest-based package format from remote servers to the local system. It works over HTTP (by default, at least). Remote sites are identified at the top-level of the mounted directory and all sites are verified by PKI signature.

AppFS is started with the appfsd daemon, which may also be named mount.appfs.

 

OPTIONS

-d
Enable FUSE debug mode.

-f
Run AppFS daemon in the foreground.

-s
Enable single threaded mode. This will significantly reduce performance and responsiveness.

-h
Request usage help.

-o nothreads
Enable single threaded mode. This will significantly reduce performance and responsiveness. This is the same as the "-s" option, provided for use in an /etc/fstab option.

-o allow_other
Allow other users to access this mountpoint (this is the default if the user running appfsd is root).

cachedir
Path to a directory to store cache database and read configuration file from. A suggested value for this for a system-wide appfsd is /var/cache/appfs.

mount_point
Path to mount AppFS onto in the filesystem. This should almost always be /opt/appfs.

 

FILES

cachedir/config
Configuration file for this instance of AppFS. This should be a valid Tcl(n) script. The configuration file can be modified at run-time and appfsd reloaded by sending it a SIGHUP.

cachedir/cache.db
SQLite3 database used for maintaining metadata for the cache directory.

 

EXAMPLES

The most recommended method of running AppFS (directly):

# mkdir /opt/appfs # appfsd /var/cache/appfs /opt/appfs

Create an /etc/fstab entry:

/var/cache/appfs /opt/appfs appfs defaults 0 0

 

SEE ALSO

Tcl(n), sqlite3(1)