Terminating Multiple Accounts
I'm trying to understand why when multiple accounts are terminated it does a restart of apache each time an account is removed.
Is there a technical reason for this or just poor design? When you delete quite a few accounts your web server may as well be offline while it's doing it.
Poor design.Originally Posted by VeZoZ
/scripts/killacct disrupts normal httpd operations
I wasn't aware it was in the bug tracker as well.
Yeah this needs to get fixed. With all the new features coming out and fixes finally coming out for other annoyances I'm surprised this problem has not been addressed yet.
No one's voted on it or commented on it, so there's no motivation for it to be fixed.
Well, I don't think a lot of the new things to pop up are in the bug tracker.
It's surprising though that that entry has no support. You'd think any decent size user using cPanel would have noticed this and complained.
Yet it still has 0 votes...
I did.You'd think any decent size user using cPanel would have noticed this and complained.
Well I voted for it.
Of course I do not expect anything to change.
I talked to support about an issue with users deleting Ruby applications while they were still running. Support confirmed it to be an issue filed a bug report and it still sits unfixed or the bugzilla entry has not been updated.
Looks like it's marked as an enhancement now which means it's doomed to never be fixed. What I've ended up having to do when getting rid of reseller accounts is logging into their reseller then terminating a few accounts at a time. It's time consuming but at least Apache functions while you're removing accounts.
Last edited by VeZoZ; 08-26-2008 at 09:49 AM.
Classifying something as Bug or Enhancement has little to no bearing on whether something will be accomplished.
You're correct. A few years ago, it depended on what dart hit the board in the developer's lounge.
The last year or so has seen a drastic improvement in what does or doesn't get fixed, improved, or added.
But I still think there is a better way then using a "voting" system that few people know about unless they stumble onto it.
Cpanel should be regularily soliciting its user base to inform it about bugzilla and how voting (determination of bug fix/enhancement priority) works.
Just my 2 cents.
I am an eNom ETP.
Sign up today if you want an eNom.com domain reseller account from a reliable provider.
* We now provide support and service to over 3250 happy resellers!
Things have been better. I always forget the bugzilla is actually viewed now (or at least it seemed like it wasn't before). I also noticed this particular issue was assigned to someone. Now whether that means it's being worked on I do not know.
QA reviews the Bugzilla system daily. Sometimes other matters take priority, thus delaying a response, but we are fully aware of all matters that come through the Bugzilla system.
Some things should really be handled via the ticket system, for a variety of reasons ( e.g. duplicability ).
LinkBack URL
About LinkBacks
Reply With Quote
