The HP-UX Parallel rc Framework

Adding rc Scripts into the Parallel rc Framework
ISV or customer products which have RC scripts can benefit from the Parallel rc Framework. The
following needs to be done:
For HP-UX11iv3:
1. An install time dependency for the product which needs to be added to Parallel rc Framework, has
to be placed on the PARLL-RC_ENH product present in the RCEnhancement bundle.
2. The product installation script has to add the dependency information of the specific rc script on
other rc scripts into the Parallel rc Framework by using the rcutil(1m) command.
For the next Enterprise HP-UX release:
Upon upgrade to the next enterprise release, the RCEnhancement Bundle along with PARLL_RC_ENH
product will not be a selectable feature or product, and the contents will be delivered by default on
HP-UX. All dependency information added by a customer or ISV for their product rc scripts have to be
added again on the new release.
1. An update to the customer product has to be provided either as a patch to the product or as a new
version of the product. A dependency must not be placed on the RCEhancement/PARLL_RC_ENH
product.
2. The product or patch install script has to add the dependency information of the RC scripts into the
Parallel rc Framework by using the rcutil(1m) command.
This section may get updated after the next mainline release.
Appendix A: Performance improvement guidelines for
individual RC scripts
In this section suggestions are provided that may improve the performance of RC scripts.
Please note that maintaining compatibility is more important than better performance.
1. Disable obsolete services by default
Disable obsolete services by default and if required customers can enable them later.
• Note: Before disabling a service it is recommended that a check be made to make sure there
are no other services which depend on the given service to be available by default.
2. Change the default settings to improve performance
Check the default settings of services, which may cause performance overheads.
For example:
LIST_TEMPS is set to 1 by default, which may not be necessary.
3. Revisit long sleeps
Some RC scripts could have delays (sleeps) added for daemon processes to get initialized before the
script can take further action. This may be because of lower processing speeds of systems with lesser
CPUs in earlier days. These delays could add to a prolonged system initialization time. Revisit the
long sleeps in the code and evaluate the best sleep time required.
• Note: If the same product is used for midrange to high-end HP-UX systems, care has to be
taken to consider the best sleep value which would satisfy all cases.
4. Avoid sourcing all system configuration variables