Linux Administration Cookbook

How to do it...

If a temporary solution buys you time, or means alarms stop going off and a website comes back online, then by all means do them, but also make a note of what you've done and log it in whatever ticketing system you use.

Be responsible for your own cludge. It's on you, and only you, to ensure that your temporary cron-job, system timer, or disk-space extension doesn't become the permanent fix for a problem.

In a similar vein, if you write a bash script to periodically check a log file, and if it's over a certain size to compress it, make sure you also write checks to ensure that the bash script is working. There's nothing more annoying than coming to a system that has a "fix" applied to it, only to discover that the bash script ...