Changes between Version 12 and Version 13 of Doc/gLite/TemplateCustomization/Services


Ignore:
Timestamp:
Mar 14, 2011, 4:18:09 PM (13 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/TemplateCustomization/Services

    v12 v13  
    368368=== DPM site parameters ===
    369369
    370 There is no default template provided for DPM configuration. To build your own template, you can look at template [source:templates/trunk/sites/example/site/pro_se_dpm_config.tpl pro_se_dpm_config.tpl] in examples provided with QWG templates.
     370There is no default template provided for DPM configuration. To build your own template, you can look at template [source:templates/trunk/sites/example/site/glite/dpm_config.tpl site/glite/dpm_config.tpl] in examples provided with QWG templates.
    371371
    372372Starting with QWG Templates release gLite-3.0.2-9, there is no default password value provided for account used by DPM daemons and for the DB accounts used to access the DPM database. You '''must''' provide one in your site configuration. If you forget to do it, you'll get a not very explicit panc error :
    … …  
    380380=== Using non-standard port numbers ===
    381381
    382 It is possible to use non-standard port numbers for DPM daemons `dpm`, `dpns` and all SRM daemons. To do this, you  need to define the `XXX_PORT` variable corresponding to the service in your gLite site parameters. Look at gLite [source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl default parameters] to find the exact name of the variable.
     382It is possible to use non-standard port numbers for DPM daemons `dpm`, `dpns` and all SRM daemons. To do this, you  need to define the `XXX_PORT` variable corresponding to the service in your gLite site parameters. Look at gLite [source:templates/trunk/grid/glite-3.2.0/defaults/glite/config.tpl default parameters] to find the exact name of the variable.
    383383
    384384''Note: this is not recommended to change the port number used by DPM services in normal circumstances.''
    … …  
    386386=== Using a non-standard account name for dpmmgr ===
    387387
    388 If you want to use an account name different from `dpmmgr` to run DPM daemons, you need to define variable `DPM_DAEMON_USER` in your site configuration template and provide a template to create this account, based on [source:templates/trunk/grid/gLite-3.0.0/users/dpmmgr.tpl users/dpmmgr.tpl].
     388If you want to use an account name different from `dpmmgr` to run DPM daemons, you need to define variable `DPM_DAEMON_USER` in your site configuration template and provide a template to create this account, based on [source:templates/trunk/grid/gLite-3.2.0/users/dpmmgr.tpl users/dpmmgr.tpl].
    389389
    390390
    … …  
    414414=== LFC site parameters ===
    415415
    416 Normally the only thing really required in this site-specific template is the password for LFC user (by default `lfc`) and the DB accounts. Look at standard LFC [source:templates/trunk/glite-3.0.0/glite/lfc/config] configuration template for the syntax.
     416Normally the only thing really required in this site-specific template is the password for LFC user (by default `lfc`) and the DB accounts. Look at standard LFC [source:templates/trunk/glite-3.2.0/glite/lfc/config] configuration template for the syntax.
    417417
    418418Starting with QWG Templates release gLite-3.0.2-9, there is no default password value provided for account used by DPM daemons and for the DB accounts used to access the DPM database. You '''MUST''' provide one in your site configuration. If you forget to do it, you'll get a not very explicit panc error :
    … …  
    430430=== Using non-standard port numbers ===
    431431
    432 It is possible to use non-standard port numbers for LFC daemons. To do this, you only need to define the `XXX_PORT` variable corresponding to the service. Look at gLite [source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl default parameters] to find the exact name of the variable.
     432It is possible to use non-standard port numbers for LFC daemons. To do this, you only need to define the `XXX_PORT` variable corresponding to the service. Look at gLite [source:templates/trunk/grid/glite-3.2.0/defaults/glite/config.tpl default parameters] to find the exact name of the variable.
    433433
    434434''Note: this is not recommended to change the port number used by LFC services in normal circumstances.''
    … …  
    436436=== Using a non-standard account name for lfcmgr ===
    437437
    438 If you want to use an account name different from `lfcmgr` to run LFC daemons, you need to define variable `DPM_USER` in your site configuration template and provide a template to create this account, based on [source:templates/trunk/grid/gLite-3.0.0/users/lfcmgr.tpl users/lfcmgr.tpl].
     438If you want to use an account name different from `lfcmgr` to run LFC daemons, you need to define variable `DPM_USER` in your site configuration template and provide a template to create this account, based on [source:templates/trunk/grid/gLite-3.2.0/users/lfcmgr.tpl users/lfcmgr.tpl].
    439439
    440440