Our application uses a chain of dot .profile configuration files to create the environment variables that numerous ksh shell scripts use. (The .profile sources .profile.abc which sources .profile.xyz, and so on.)
The problem with this approach is that there is not one centralized file where all these configuration settings live. This method of setting the application configuration is causing endless problems. We have inherited this and are looking a "painless" solution due to all the scripts that require environment variables.
One suggestion was to create a ksh function to look up values from a configuration file and to use this function in all assignments in the ksh script. This would bypass having a multitude of environment variables.
Is there a solution where I could use Perl to centralize the configuration settings, but still provide the proper shell environment for older scripts? Right now we must source the .profile chain before running any scripts or middleware from the shell.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.