Efficiency in what domain? Execution time is probably not a large concern (imo), because the time that it would take to start the Apache process will likely outweigh any amount of perl code that would be doing the checking.
I would be asking myself about the most efficient way to manage the maintenance of these lists. Does the set of Apache processes change? Do you need to allow other people to manage this list? Does this list of Apache processes need to be able to be moved around to different back ends?
Your solution for storage of this list may end up being a simple my @host_list, a configuration file with the necessary information that can be re-read as necessary, all the way up to a DB (small as it may be) where each back-end is able to start and stop Apache servers as the configuration changes.
--MidLifeXis
In reply to Re: Efficient Automation
by MidLifeXis
in thread Efficient Automation
by jmneedhamco
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |