Given the amount of resources a bash script can consume, along with any possible service impact it might have, I have been trying to compile a list of 'testing controls' to benchmark any script against before using it on any Check Point device by carrying out the following steps in a lab environment:
1) Observe the resources being consumed by the script. This can be done by having two additional Putty sessions open and run the following commands :
- watch free -m
- top
2) Ensure that there is no service impact by monitoring critical services such as VPN tunnels etc.
3) Ensure that only a specific group of admins have execution privileges over the script.
I would appreciate other people's feedback on this topic, particularly of guys like @Robert_Decker and @Danny who are well versed in the art of scripting. My point is that I am after a process to follow when creating scripts for Check Point devices in order to get the maximum value while causing the least possible amount of disruption.
Thanks in advance!