Thursday, April 28, 2005

Bzzt! Does not compute.

I spent the last TWO DAYS trying to figure out why the software I'm writing had gone all cracky. Access times went from less than a quarter second to half a minute.

I was picking through my code - what was it? The code was tight as a drum. It couldn't possibly be the code. Maybe one of the external functions I was using was taking up dramatically more time than I thought? Well, not that one... or that one...

I finally figured out the problem: I was running 'arp' and it never occurred to me that Linux would HANG on arp for thirty seconds. Turns out I had an amorous Windows server frantically trying to back up my Linux box. Since it's the only Linux box on the network, neither knew how to handle the situation. Furthermore, for reasons unknown to me, the Windows box REFUSED to respond to pings while trying to back up the system.

Worse, if I rebooted, it just reconnected. Until IT gets around to fixing the problem, I just cut that segment out completely. I'll live, although it creates a security hole. In a system specifically (and at request) created to be as secure as tissue paper. I'm not worried.

Now the code runs lightning fast again. Ah, code looks real tight after the fourth rewrite.

If you've gotten this far, you really need something more interesting to read. Honestly. Listening to me mutter about work-related projects ranks right up there with playing solitaire.

1 comment:

Darius Kazemi said... I take a break from my Solitaire game to read your blog...