Well, they did track back and tried pointing it back at him..but you know something really weird? The exact SAME time he was editing the crontab someone else was also editing it!! So this guy saved and exit and AFTER that the other guy quit and exit without saving! SO whatever changes he did the first time was overwritten and the fault was GENUINE. But to do that TWICE in two weeks!!!?? He wasn't fired but he left after 6 months of working, he didn't like the working culture there. They don't fire people for that, it was filed under "human-error"
---------- Post updated at 10:05 PM ---------- Previous update was at 10:00 PM ----------
Quote:
Originally Posted by
spynappels
Was he fired? If I was his manager and had any suspicion that he was responsible and was able to prove it, not only would he be fired, he'd also be prosecuted for criminal damage!
He wasn't fired, was filed under "human error" because two people were editing it at a same time but the customer was duly compensated. This is just the kind of thing that happens on daily basis over there. He err'ed the first time I admit but I was suspicious when he err'ed again the following week.
---------- Post updated at 10:16 PM ---------- Previous update was at 10:05 PM ----------
..dont get me started on the 1st level support guy whom renamed a system to a single numeric value of "2" His excuse was that he wasn't aware what uname -S does in UNIX..last I checked he's still there