tembak. that's a bad thing right? all google has is stuff in (possibly) malaysian? but certainly has a familiar, rather sinister ring to it. and the 95% server resources it was hogging didn't make me feel real fuzzy towards it either. but in order to kill it, i have to find it. it's a big server.
i was going to go into how exactly much i don't know about this, but instead i'll get back to scowling pensively at the various server administration thingys i have open.
* * * * *
oh.my.god. so i ran the apache upgrade because it said it was insecure, and because tembak is a malicious somethingorother, being run from two different IPs i traced to Jakarta, Indonesia. so i upgraded. and apache crashed, ftpd crashed, mysql crashed, and ... right, exim. so, the server was fine except for not having database access, email, ftp, or the ability to serve pages to a browser. full reboot got apache started well enough to be able to deliver some lovely error messages. restarted mysql, restarted ftpd. exim is taking its time.
how were the goddamn indonesians running tembak on the server? i need some tequila.
* * * * * *
UPDATE TO THE UPDATE
the upgrade of apache is won't run PHP files CHMOD 777 which is like, most of them, because it's world writable do you have any idea how many fucking PHP files there are on these goddamn servers?
so i finally figured out it's
find / -name *.php -exec chmod 755 {} \;
otherwise i think i might have had to do something drastic. goddamn motherfucking piece of shit computers.
* * * * * * *
* * * * * * *
ANOTHER MOTHERFUCKING UPDATE
i can fix 'em all i want but one MT rebuild sets 'em back to 777 and kablammo. fuck.
know what? i'll be back. i need to go get beer.
