![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Apr. 26th, 2002 02:22 pmIt has been a very strange 12 hours, professionally.
I've been playing with side-job #1, which involves some telephony code I wrote back in '98. I've been hacking and hacking, and I'm finally getting to the point where the thing looks like some sort of Boy Scout first aid manual. It's all patches and splints and ace bandages, with not too much substance any more. And the movement is pretty restrictive as well. I'm thinking I'm going to have to rewrite major chunks of it from scratch. May not be a bad thing in the long run, but it is a setback.
Then, this morning, an old client calls me up (let's call this side-job #3). He's having problems with his server again. This is something that ran just fine in a closet for months; nobody has touched it. The last couple of weeks, it's just been dog slow and acting very bad. A bit of this project involved sending email status reports, and the email is sometimes 6 to 12 hours slow. So I head over to the colo place during lunch today to see if I can debug it from there instead of remotely. I notice the email program is taking up 99% of the CPU so I take a look at the logs. Bah. I've been hacked. Some fuckwad is using my email machine to send spam. The email program was busybusybusy and bringing down the rest of the system. I have it shut down right now, and I'm logging all attempts to use it to send email. My colo is very interested in the IP address of the offender. If it's internal (some other customer in the colo), they're gonna kick the guy out. If it's from outside, that's most likely interstate theft of service and they're gonna call the FBI on 'em.
I've been playing with side-job #1, which involves some telephony code I wrote back in '98. I've been hacking and hacking, and I'm finally getting to the point where the thing looks like some sort of Boy Scout first aid manual. It's all patches and splints and ace bandages, with not too much substance any more. And the movement is pretty restrictive as well. I'm thinking I'm going to have to rewrite major chunks of it from scratch. May not be a bad thing in the long run, but it is a setback.
Then, this morning, an old client calls me up (let's call this side-job #3). He's having problems with his server again. This is something that ran just fine in a closet for months; nobody has touched it. The last couple of weeks, it's just been dog slow and acting very bad. A bit of this project involved sending email status reports, and the email is sometimes 6 to 12 hours slow. So I head over to the colo place during lunch today to see if I can debug it from there instead of remotely. I notice the email program is taking up 99% of the CPU so I take a look at the logs. Bah. I've been hacked. Some fuckwad is using my email machine to send spam. The email program was busybusybusy and bringing down the rest of the system. I have it shut down right now, and I'm logging all attempts to use it to send email. My colo is very interested in the IP address of the offender. If it's internal (some other customer in the colo), they're gonna kick the guy out. If it's from outside, that's most likely interstate theft of service and they're gonna call the FBI on 'em.
