Overview

Artifact ID:	eb44e6f2d286a49c6bf91ee434d9de637646a763
Page Name:	Manual
Date:	2014-02-07 20:41:56
Original User:	rkeene
Parent:	731b14f997b8908deb794f55b58e9c82a4dfe8ab (diff)
Next	b354969590af219f2fa07bb42ac2955f61cf1775

Content

FILED

Section: User Commands (1)
Updated: 06 Feb 14
Index

NAME

filed - serve files over HTTP

SYNOPSIS

filed

--help}

--bind} address

--port} port

--threads} count

--cache} entries

--user} user

--root} directory

DESCRIPTION

FILED

serves files over HTTP as minimally as possible. Only static files (i.e., files that never change or are replaced) are supported.

OPTIONS

-h (or --help)

Prints detailed usage information

-b (or --bind)

Specifies the address to listen for incoming HTTP requests on.

-p (or --port)

Specifies the TCP port number to listen for incoming HTTP requests on.

-t (or --threads)

Specifies the number of worker threads to create. Each worker thread can service one concurrent HTTP session. Thus the number of threads created will determine how many simultaneous transfers will be possible.

-c (or --cache)

Specifies the number of file information cache entries to allocate. Each cache entry holds file information as well as an open file descriptor to the file, so resource limits (i.e., ulimit) should be considered. This should be a prime number for ideal use with the lookup method.

-u (or --user)

Specifies the user to switch user IDs to before servicing requests. The default is not change user IDs.

-r (or --root)

Specifies the directory to act as the root directory for the file server. If this option is specified, chroot(2) is called. The default is not change root directories, that is, the "/" directory is shared out. This will likely be a security issue, so this option should always be used.

AUTHOR

Roy Keene <filed@rkeene.org>