best practice for similar linked tasks?

Posted on

best practice for similar linked tasks? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, scripting, , , .

I’m setting up a server for a small office, that is accessable from the internet. Since our ISP has a transparent proxy, most dynamic dns services fail, other than dyndns (who isn’t our provider) so we use a script to set it manually- it connects to dyndns, fetches a web page with the info, strips the ip address out, and sets the ip address for a single domain via a web request to our actual dns provider. This whole process is run once an hour by crontab

If i wanted to extend this to more than one hostname, would it be a better idea to have one script running per hostname (ie, single script for obtaining the ip address, and one per hostname) or to have a single monolithic task for the whole thing?

Solution :

I don’t think there’s any one answer to this. Having multiple scripts will make it easier to turn it off on a hostname-by-hostname basis. On the other hand it will somewhat increase the maintenance overhead by giving you more places to look. Personally I would do it all in one script unless there was a really compelling reason not.

Leave a Reply

Your email address will not be published. Required fields are marked *