Considering that I identified the problem WEEKS ago without even having access to the server..... ya, I'd say he's not really capable of fixing it. If it takes you weeks to fix something thats already been identified, then you cant really say you 'fixed' anything. If you took a vehicle to a repair shop, told them that the battery was dead and then they proceeded to try every test EXCEPT the battery, would you consider them competent mechanics if they eventually changed the battery 3 weeks later?
Yes, i agree with your analogy.
That was definitely my fault.
Below is the bad cronjob
0 21 * * * Do Something here
And here is the fix.
#0 21 * * * Do something here
Just a technical note from me: There was not "0 21 * * * Do Something here", otherwise i'd comment it. I think that was someting like /etc/cron.daily, i still didn't find anything suspicious there...
Nothing suspicious in crontab also.
Of course that doesn't excuse me, just a note. Definitely my fault.
*in sackcloth and ashes*
Please, stop making excuses for everyone. It's his job as server administrator to do all these things...
Your rhetoric against me have been changed definitely 3 weeks ago.
I'd say that was a reason for my idling and apathy.
I didn't expect that your turn from my friend to my enemy will make me so sad.
Well, i hope i almost got it, so i hope to revive my activity for the server.
