Chapter 1
How to write the GANESHA’s
configuration file
1.1 Overall view of the configuration file
The configuration file for the GANESHA daemon may seemed huge at first glance. It is separated
into several blocks. A block contain several items.
A block will look like this:
<BLOCK_TAG>
{
<Config_Item_Tag> = <Value> ;
# Comment
<Config_Item_Tag> = <Value> ;
.
.
.
<Config_Item_Tag> = <Value> ;
}
As we will see, there are many different blocks, each of them dedicated to the configuration of
a specifc stuff in GANESHA. Not all the blocks are mandatory and some may not be explicitely
specified. In this case, default values will be kept¿ Inside the blocks are items which are a way
to set a internal constant in the daemon with direct effect to the program’s behaviour. Like the
blocks, not all the items are mandatory and some may be lacking. The following sections will
described each blocks and items and explain all of them and their use.
Block’s names and item’s name matching algorithm is case insensitive. Naming a block EX-
PORT or Export or export work as well.
Every character below a ’#’ sign is a comment and will be ignored (except if it is inside a
quoted string, or escaped with a backslash).
You can also include annexe configuration files using %include statement:
E.g:
%include "annexe_file.conf"
3