kimo wrote:
> Edgar wrote:
>> I have sections global to all, then chunks of data seperated by the
>> type of machine the config is to run on with html style '<CONFIG-TYPE>
>> </CONFIG-TYPE>' where they need to be so the flow of the
>> file is never broken as to when a partcular chunk is to be run. I
>> even have the file fill-in machine specific information such as
>> hostnames, or node numbers, etc, with <$CONFIG> statements
>> 'host_name=<$CONFIG>'. Some, or most would find this terribly
>> confussing but i like it very much as I have lots of machines that are
>> the same as for OS build, but need to do different things. This way I
>> can just roll out one master file to all and not worry about it.
>
> I would like to see this file and your scripts. I have several servers
> that have basically identical setups except for hostnames, IP address,
> etc. That type of setup would help me alot.
>
> Thanks
> Kimo
>
--
Okay, at leaset one person wanted to look at this, and I finally got them
posted to a website, (although very bare..), there is also a script file
I use to help maintian exim db and spool files, I put it up also as there
seem to be an overwhelming number of people that keep asking, 'how do get
rid of 1000+ frozen messages???'
At any rate, you can find them here:
http://members.cox.net/exim-list/
and you can email should you have any questions or suggestions.
Cheers!
--EAL--
