Installing Disco System-Wide¶
Install From Source¶
Note: On FreeBSD, replace all of the instances of make with gmake.
Assuming you have already gotten Disco running out of the source directory,
as described in Install Disco,
to install system-wide, just run
make install as root:
This will build and install the Disco master to your system
Makefile for exact directory locations).
You can specify
in compliance with GNU make.
On systems that are intended to function as Disco worker nodes only,
you can use the
make install-node target instead.
make install installs a configuration file to
that is tuned for clusters, not a single machine.
the settings assume that you have at least three nodes in your cluster,
so DDFS can use three-way replication.
If you have fewer nodes,
you need to lower the number of replicas in
DDFS_TAG_MIN_REPLICAS=1 DDFS_TAG_REPLICAS=1 DDFS_BLOB_REPLICAS=1
Most likely you do not need to modify anything else in this file right now, but you can change the settings here, if the defaults are not suitable for your system.
disco.settings for more information.
Creating a disco user¶
You can use any account for running Disco,
however it may be convenient to create a separate disco user.
Among other advantages,
this allows setting resource utilization limits for the disco user
limits.conf or similar mechanism).
Since Disco places no special requirements on the user, (except access to certain ports and the ability to execute and read its files), simply follow the guidelines of your system when it comes to creating new users.
Keeping Disco Running¶
You can easily integrate
into your system’s startup sequence.
As an example, you can see how
is implemented in Disco’s
Configuring DDFS Storage¶
On the Disco nodes, DDFS creates by default a subdirectory named
vol0 under the
DDFS_DATA directory to use for storage.
If you have one or more dedicated disks or storage areas you wish to
use instead, you can mount them under the directory specified by
DDFS_DATA as subdirectories named
vol1 and so