Read logs before editing configs
A tiny habit that prevents many unnecessary configuration changes.
When a service is already running, logs usually explain more than the config file alone. They show what the process actually loaded.
Before editing, capture the current listener list and recent service log. After editing, capture the same facts again.
This turns maintenance from guessing into comparison.
Filed under: diagnostics