Source-diving as a system administrator
blog.ksplice.com
blog.ksplice.com
- environment variables changing the behavior of the program
- load-dependent pthreads issues (can't reproduce on unloaded dev machine)
- shell scripts silently failing to do important things (liking kill off the old processes; but there's a check to not spawn if it's already running)
- config files that looked fine (realize that there's a case sensitivity issue in 1 out of 5 of the config files)
The simplest patches also the best. Fixing a single configuration option that is just not provided is the simplest and best monkey patch. Dealing with any logic will get scary over time.
But have you seen them abused as "additional" parameters to a function? putenv() by the caller, getenv() by the callee, rejoice!