

Oh it happens to the best of us. I was working on a simple cron the other day with the cron string that would insert the cron into my cron config something like ‘echo’ and the normal string you’d recognize, and ended with a ‘-’. I wasn’t paying attention and issued the command which did insert itself into the cron config, but in a manner in which I didn’t want. It replaced the whole cron file with that one string. #$@^$$ Luckily I have a cron to back up the crontabs.
I’m kind of that way. I will browse documentation, get a good idea as to what has to happen, then I raw dog it. Then, after many failed attempts, I go read the documentation. I agree with [email protected] tho, a ton of documentation either assumes you are a certified, dyed in the wool, sysadmin veteran with a wall of certs, or it’s just too sparse for me to put together.