EPREPARE(1) OpenBSD Reference Manual EPREPARE(1)
NAME
eprepare - create epitome database
SYNOPSIS
eprepare [-c] [-D backend_name] [-d depth] [-N hostname]
[-O optional_config] [-S hostport] [-T backend_type] [-U user]
DESCRIPTION
The eprepare command prepares the epitome backend for use.
One of the following flags must be present:
-c Create a backend database.
In addition to the flags mentioned above, any of the following flags may
be used:
-D backend_name
Depending on the backend_type this value is the identifier of the
backend. For example for the file type, this is the target di-
rectory of the backend.
-N hostname
When running over the network this is the hostname of the epitome
server.
-O optional_config
Depending on the backend type this contains optional configura-
tion data. As an example, when using the raw bakend one has to
select a raw device. For example -O /dev/rsd1c.
-N hostname
When running over the network this is the hostname of the epitome
server.
-S hostport
When running over the network this is the hostport of the epitome
server. Default is 1337.
-T backend_type
Select backend type. Currently supported types are file, bdb,
and raw. There is an experimental Postgresql backend.
Note: when using the file backend one should use a filesystem
with many inodes and a block size roughly the same as the epito-
mize block size.
-U user
When using with a database type, this is the database user.
-d depth
When using the file type one can select the depth of directories
used to store shas.
EXAMPLES
The following command illustrates how to create a backend database:
# eprepare -T file -cD /var/epitome
SEE ALSO
epitomize(1), epitome(3), epitome.conf(5)
HISTORY
The eprepare command first appeared in OpenBSD 4.5.
AUTHORS
The epitome suite was written by Marco Peereboom <marco@peereboom.us>.
CAVEATS
The epitome suite is currently considered experimental.
Beware that when using the file backend on a local machine security is
only as good as file permissions.
OpenBSD 4.4 October 6, 2008 2