knoxhosting
Verified User
- Joined
- Jan 10, 2005
- Messages
- 42
A process killer would be nice on the admin level.
Process killer
- Thread starter knoxhosting
- Start date
In addition to the programs already available in the service Monitor? Such as a page with all information (processes) displayed by top and an input box for pid or link next to them to kill them?
Personally, I don't see the point, since I'm always logged in and have a console available. And chances are if any application created such a high load requiring a kill of a process, you probably wouldn't have a very good chance killing that process with DirectAdmin. Console (or ssh) would be your best bet since they have slightly higher cpu priority
But that's just my opinion
Care to share you reasons why you feel it would be a valuable addition to DirectAdmin? (Other than, because it's cool or because control panel so and so does it..) You may even convince me
Personally, I don't see the point, since I'm always logged in and have a console available. And chances are if any application created such a high load requiring a kill of a process, you probably wouldn't have a very good chance killing that process with DirectAdmin. Console (or ssh) would be your best bet since they have slightly higher cpu priority
But that's just my opinion
Care to share you reasons why you feel it would be a valuable addition to DirectAdmin? (Other than, because it's cool or because control panel so and so does it..) You may even convince me
Last edited:
knoxhosting
Verified User
- Joined
- Jan 10, 2005
- Messages
- 42
It's not that useful for killing ONE process, but follow my logic...
Yeah, like top. I hate to say it, but like cPanel does it. Click on a link to see all running processes and their owners. The PID is clickable on all the processes, which takes you to a nother screen where you can get more information about the process. More buttons are here that offer you the ability to Kill just that process or All processes owned by that user.
Case in point. One of my old linux boxes several years ago got hijacked by a customer who got upset after I told him he needed to pay for his service or I was going to suspend his account. He said, fine, I'm going to F up your server then and hung up. I was on a cell phone and knew it was a race against the clock to get home and beat him to a login. I didn't beat him, but he was a moron on thought he'd wreck the server by just starting a bunch of scripts up. Anyway, using cPanel's Show All CPU Processes feature, I was able to quickly see all processes running, and kill every process running in his account without having to go to shell. I'm okay in shell, but I'd prefer doing stuff in the control panel if I can.
Also, I'm in the habit of logging in places where there is no SSH access. A control panel feature like this would not require SSH access to stop processes.
It'd be a good addition to DA because it would add a new level of control right there within the control panel - the ability to see EVERYTHING going on inside that server. Not one thing missed. "Where's my RAM going?! Oh, there... what's that program? Who's running that?!"
It's better than using top, because top is limited to however many rows your terminal window can display.
Yeah, like top. I hate to say it, but like cPanel does it. Click on a link to see all running processes and their owners. The PID is clickable on all the processes, which takes you to a nother screen where you can get more information about the process. More buttons are here that offer you the ability to Kill just that process or All processes owned by that user.
Case in point. One of my old linux boxes several years ago got hijacked by a customer who got upset after I told him he needed to pay for his service or I was going to suspend his account. He said, fine, I'm going to F up your server then and hung up. I was on a cell phone and knew it was a race against the clock to get home and beat him to a login. I didn't beat him, but he was a moron on thought he'd wreck the server by just starting a bunch of scripts up. Anyway, using cPanel's Show All CPU Processes feature, I was able to quickly see all processes running, and kill every process running in his account without having to go to shell. I'm okay in shell, but I'd prefer doing stuff in the control panel if I can.
Also, I'm in the habit of logging in places where there is no SSH access. A control panel feature like this would not require SSH access to stop processes.
It'd be a good addition to DA because it would add a new level of control right there within the control panel - the ability to see EVERYTHING going on inside that server. Not one thing missed. "Where's my RAM going?! Oh, there... what's that program? Who's running that?!"
It's better than using top, because top is limited to however many rows your terminal window can display.
Last edited:
You gave a good explanation knoxhosting. I could see the usefulness in it, especialy killing all processes for a particular user. Combined with suPhp which would make php scripts run under the correspond user (right?), you could also easily kill runaway php scripts.
But I agree with rldev, there are other features that are needed (to be finished) that are probably higher priority.
But I agree with rldev, there are other features that are needed (to be finished) that are probably higher priority.
knoxhosting
Verified User
- Joined
- Jan 10, 2005
- Messages
- 42
Thanks for considering it. Every new feature just adds to the list of things that make DirectAdmin a very good competitor with the "other control panels" out there.