Context Navigation

Services

v24	v25
387	387	* `DPM_SERVICE_PARAMS`: configuration parameters for each service, to be applied to all hosts running the service. This variable is a nlist where the key is one of the value valid for `DPM_HOSTS`. The value must be a nlist specifying the value for each configuration parameter specified. The exact list of parameters possible depends on the service. For the exact list, look at NCM::Component::dpmlfc man page or at [source:templates/trunk/grid/emi-2/components/dpmlfc/schema.pan schema]: valid values are those under the `dpmlfc_xxx_node_config` appropriate the service.
388	388
	389	''Note: there is no need to add the DPM head node to the disk server list if it is not acting as a disk server. For protocols like `rfio`, where the daemon is required to run also on the head node, the templates will do what is appropriate. And if you disable `rfio` as an access protocol, the configuration will ensure the daemon is still running on disk servers for DPM internal use.''
	390
389	391	If you want to use a specific VO list on your DPM server and you have several nodes in your DPM configuration (DPM head node + disk servers), you need to write a template defining `VOS` variable (with a non default value) and define variable `NODE_VO_CONFIG` to this template in the profile of DPM nodes (both head node and disk servers).
390	392