Quote:
Originally posted by Rich Z
That errant process is running on my serverf again causing the slowness experienced yesterday. I'm trying to get the tech support people at my server host to fix the problem, but they seem to be dragging their feet on me. Man, that's all I will need is to have to switch server hosts right now.....
|
There's probably something sat in the cron that keeps firing it up.
You can type...
ps waux | grep wusage
In order to get the applications pid.
If it's owned by your userid (or you have root access) you can...
kill -9 <the process id>
By the fact that you mentioned the ability to reboot the server, I would assume you have root access.
But, this is just a short term fix and not really going to help much - as the program will automatically reload itself once the system spots it's not up and running. You'll have to start hunting through the cron & init scripts by the sound of it (have a look in /etc/rc.d or /etc/init.d depending on what Linux distro is powering this baby).
Doing the ps waux | grep wusage will also tell you the username under which the application is running. If you have root, or it's running under your own username, you can do...
crontab -l -u <username>
If something comes up, you can just edit it there. If not, check the runlevel inits.
Katie: Nope, not a virus. The only successful virus ever written for Linux was called "Melissa", and it was stamped out in the Kernel a coupla years ago - the only threats these days are backdoors, trojans, etc. But they're limited to the abilities of the username under which they're executed (hence the reason advice is usually given to rarely use the root account except for system administration, and not general usage - just in case).
Edit - Heh, ok, I didn't read your other response Rich. So, it is in the cron and you don't have root access? Hmm... sounds a bit odd considering it's supposed to be a dedicated box - especially with the money you're paying. But, still, best of luck with it