I always like to test new config files before deploying them--with tools like apachectl configtest
and named-checkconf
.
It's rare that mistakes crop up, but catching them before deployment eliminates any impact. The one that has bit me in the backside several times is /etc/network/interfaces
; I can't seem to find a tool to test it, and restarting the network on a remote machine only to discover it's no longer reachable is quite annoying--especially when we use a lot of bonding and bridging.
To expand upon @jdthood's answer...
If the interface is already up, you can still use this method to validate the
/etc/network/interfaces
file. For example, assuming you have an error, you may see something like this:Apparently there's an error on line 11. Great. Thank heavens I didn't bounce the networking only to lose SSH access!
If all is fine, you will see:
The following may do part of what you want.
If you don't have a eth0 this will not work, eg:
But if you do like this:
With ok config:
With non-ok config: