Changes between Version 156 and Version 157 of Doc/gLite/TemplateCustomization

Timestamp:

Feb 8, 2010, 10:57:31 PM (16 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/gLite/TemplateCustomization

@@ -481 +481 @@
  * `CE_WN_ARCH`: OS architecture on CE worker nodes. Due to limitation in the way this information is published now, this is a CE-wide value. If you have both 64-bit and 32-bit WNs, you must publish 32-bit (`i386`). Default value is based on CE architecture.
 
-=== CREAM CE Specific Configuration ===
+=== CREAM CE Specific Configuration === #CREAMConfig
 
 CREAM CE has some unique features and requirements, not available in LCG CE, that can be easily customized with QWG templates. 
@@ -527 +527 @@
  * `GLEXEC_LOG_DIR`; location of glexec log files. '''This must be different from the 2 other log locations''' because the permissions are not compatible (none belong to `root`). Default: `/var/log/glexec`.
  
-CREAM CE relies on ''BLParser'' to interact with the batch system and get status back about submitted jobs. The BLParser must run on a machine with access to the batch system logs. The default is to run it on the LRMS master, which can be defined explicitly with variable `LRMS_HOST` and defaults to the first CE in `CE_HOSTS`. For specific needs, it is possible to define explicitly the BLParser host with variable `BLPARSER_HOST`.
+CREAM CE relies on ''BLParser'' to interact with the batch system and get status back about submitted jobs. The BLParser must run on a machine with access to the batch system logs. The default is to run it on the LRMS master, which can be defined explicitly with variable `LRMS_SERVER_HOST` and defaults to the first CE in `CE_HOSTS`. For specific needs, it is possible to define explicitly the BLParser host with variable `BLPARSER_HOST`.
+
+If experiencing difficulties during the initial installation, be sure to read [/wiki/ReleaseNotes/gLite-3.2 release notes#KI3203CREAMCE].
 
 === Home Directories of VO Accounts ===