arc.conf(5)

1arc.conf(5)                      NorduGrid ARC                     arc.conf(5)
2
3
4

NAME

6       arc.conf - ARC services configuration
7
8

DESCRIPTION

10       ARC has two separate configuration files - one for client tools and an‐
11       other for services. This man page describes the services  configuration
12       file.  For client configuration please see "ARC Clients User Manual" at
13       http://www.nordugrid.org/documents/arc-ui.pdf
14
15       This man page IS NOT the ultimate source of information about arc.conf.
16       The  reference  documentation  containing  all configuration option de‐
17       scription  is  arc.conf.reference   file   that   can   be   found   in
18       /usr/share/arc/doc.
19
20       To get inline help about particular configuration option use arcctl (1)
21       tool.
22
23       For example to get description of sessiondir option in [arex] block run
24
25              # arcctl config describe arex sessiondir
26

BASIC STRUCTURE

28       A block configures an ARC service, a service interface, a utility or  a
29       subsystem.   Enabling (turning on) a functionality, a service or an in‐
30       terface requires the presence of the appropriate  configuration  block.
31       To  disable a service or an interface, simply delete or comment out the
32       related arc.conf block (you may need to rerun the corresponding startup
33       script).
34
35       A  block  is identified by its block header. A block header may consist
36       of keywords and optionally block identifiers. Keywords may be separated
37       by  "/"  and  used  to  label subblocks (e.g. [arex/jura]), while block
38       identifiers are separated by ":" from keywords.
39
40       For example, in the [queue:short] block header queue is a keyword while
41       short  is an identifier, e.g. the name of the queue. Block headers must
42       be UNIQUE.
43
44       A block starts with a unique [keyword:identifier] blockheader and  ends
45       where  the  next block starts, that is at the next [blockheader] direc‐
46       tive.
47
48       A block may have sub-blocks e.g. the various  interfaces  of  the  AREX
49       service  are  configured  via  sub-blocks (e.g. [arex/ws]). When a sub-
50       block is enabled then the corresponding parent block MUST  also  appear
51       in the arc.conf file.
52
53       Configuration  blocks  contain (config option, config value) pairs fol‐
54       lowing the syntax: config_option=value element [optional value element]
55       in single line.
56
57       Each  of  the  configuration  options have well-defined default that is
58       specified in this reference file. The default can take either a pre-set
59       value,  a  special substitution or the keyword undefined. Configuration
60       options within an enabled block take their default values in case  they
61       are missing (or commented out). Configuration parameters with undefined
62       defaults takes no values.  Furthermore,  configuration  options  within
63       disabled blocks takes no values either.
64
65       Configuration  blocks related to authorization are ORDER-DEPENDENT! The
66       authorization blocks [authgroup:name] MUST be defined  before  used  in
67       the  other  blocks.  Furthermore, the order of the authorization blocks
68       itself may have influence over authorization decisions!
69
70       Note that quotes around the configuration value(s) must NOT be used any
71       longer.
72
73       Note that the arc.conf is CASE-SENSITIVE!
74
75
76

FILES

78       /etc/arc.conf, ${ARC_LOCATION}/etc/arc.conf,
79
80

REPORTING BUGS

82       Report bugs to http://bugzilla.nordugrid.org/
83
84

COPYRIGHT

86       APACHE LICENSE Version 2.0
87
88

AUTHOR

90       ARC    software   is   developed   by   the   NorduGrid   Collaboration
91       (http://www.nordugrid.org), please consult the AUTHORS file distributed
92       with    ARC.    Please    report   bugs   and   feature   requests   to
93       http://bugzilla.nordugrid.org
94
95