Reminds me of...
... a company I worked for - All the on-call staff moaned about being called up for pointless disk alerts, such as a database filesystem being 99% used - which was correct, the database tables had been sized to fill the filesystem, though the sparse tables themselves might be empty. When I asked one of them why they didn't do something about it, such as fixing the monitoring, he replied "But then I wouldn't get my callout payments"! Due to that sort of attitude, I didn't stay there long enough to be put on-call myself.
And, speaking of sparse files, how many people does it take to make a logic bomb?
- One Systems Programmer to insist his utility directory, /u, should be first in the search $PATH, as he had a custom version of tar that could handle sparse files correctly. OK-ish so far.
- One fat-fingered sysadmin to type "ls > pg" in the /u directory, instead of "ls | pg". Still not a problem, as the "pg" file is not executable.
- One zealous sysadmin to decide everything in /u should be made executable. Oops, the garbage "pg" file is now used instead of the system utility.