![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Graph generation | wadhwa.pooja | Shell Programming and Scripting | 2 | 02-05-2009 07:54 AM |
| The iPhone Generation | iBot | Cartoons for Geeks | 0 | 09-27-2008 02:30 PM |
| report generation | gmahesh2k | UNIX for Dummies Questions & Answers | 2 | 05-16-2008 02:41 AM |
| 2nd Generation SOA = EDA + CEP? | iBot | Complex Event Processing RSS News | 0 | 11-28-2007 08:30 PM |
| Shellcode Generation using C | Legend986 | High Level Programming | 2 | 10-08-2007 02:25 AM |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
Config Generation
I'm looking for good ways to handle config generation. I have been rolling my own for a few years now, but I'm wondering if there is a better way and would like to get some advice from anyone who has any ideas or experience in doing this. Here are some things I want to achieve in generating separate config files per host/service: 1. Common options shared across all configs and changed from a single place 2. Host/service specific options 3. Replace generic options with host/service specific ones 4. Some generic options may be set as non override-able Daemon features are welcome although I'm primarily looking at a daemon independent way of creating unix config files...
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|