Starting with H-Sphere 2.5, you can't customize some major service configuration files
(for Web, mail, DNS, databases, etc.) directly, as your changes in these files will be overwritten with the next H-Sphere update!
Instead, you need to create config file templates by means of H-Sphere updater
and customize these templates instead of default config files.
Please carefully study this document to re-customize:
Starting with hsphere-update-1-1-3,
all default config file templates, except for /etc/resolv.conf, are included into the
hsphere-update package and installed in the following locations:
You can customize config file templates by means of H-Sphere updater, provided you have not customized your templates already.
For this purpose two new options are added to the
hspackages wrapper of the H-Sphere update script:
hspackages ctemplates=httpdcp,php,httpd,ftpd,mysql,pgsql,named [OPTIONS] -
Place custom templates for comma-separated list of services into predefined locations if custom templates are not there already.
hspackages edit=IP:/path/to/custom/template - Edit custom template on a specified server in a specified location.
Important:
If you run the hspackages ctemplates command without options, it will create custom templates on
all related servers of the H-Sphere cluster!
To specify particular servers where custom config templates
should be created, please use the extended syntax of the
hspackages command. For example,
to create PHP custom config templates only on the physical boxes 192.168.1.10 and 192.168.1.11, run:
The hspackages ctemplates command should be run only once,
in order to create custom config templates! Then you customize these files according to your needs.
Next time you run it, it will prompt re-creating your custom config templates, thus you may lose your customization! Note:
The only exclusion when you need to run hspackages ctemplates again is when
a coming version of the hsphere-update package contains
updates of default config templates. You will be specially notified of this in the respective update notes.
CP Apache
Default CP Apache httpd.conf template is insluded into the hsphere-update and installed here:
To immediately apply changes, run the conf file generating script which is as a rule executed in the postinstall section
of the package:
/hsphere/local/config/bind/scripts/config_bind
Bind earlier than 9.3.3 RC 1
To leave /etc/resolv.conf unchanged during the update when MyDNS is used, perform:
touch /etc/resolv.conf.custom
If the latter file exists, then you can customize your /etc/resolv.conf file without the risk of
its being overwritten.
Important: Starting with hsphere-bind-9.3.1-2,
the directive include ~named/local/custom.conf is added into /etc/named.conf.
Customizing Other Files Included into H-Sphere Packages
WARNING: It is not recommended that you customize
the files included into H-Sphere packages by yourself. Any alterations made to them are at your own risk!
Besides customization of some major service configuration files (for Web, mail, DNS, databases, etc.), we have implemented
for your convenience a possibility to customize other files included into H-Sphere packages. For this, we have created a
configuration file /hsphere/local/config/customs/customs.conf and a special template /hsphere/local/config/customs/customs.conf.tmpl that will help you to save customized H-Sphere packages files during future
updates.
To customize a file included into H-Sphere Package and save the changes:
Make necessary changes to the file you want to customize.
Copy a template of custom files to a configuration file:
Please note that during the package updates all custom files will be saved in the
/hsphere/local/config/customs/$package_mask/ directory. The default files of H-Sphere packages,
in their turn, will be stored at /hsphere/local/config/customs/default/$package_mask/. The above
mentioned locations store the latest versions of both custom and default files, no matter custom or default file
is being used.
