Disabling DirectAdmin?

[animuson]

Ok, I was thinking about why I am using DirectAdmin since the only thing I ever use it for is the File Manager, which is included in a different panel that comes with the VPS, but I don't want to uninstall it because I don't know exactly what it would do or how to even uninstall it. Anyways, if I just stop the directadmin process and cancel my license, would everything on my server still work alright just unable to use the DirectAdmin features?

I'm really not sure how DirectAdmin works, but I'm trying to optimize my server a little more and after looking at the top results there is a lot of stuff running, especially the mail servers. There's only about 20 things at the top and then like 30 mail processes below it. Is it possible to reduce the amount of virtual memory that the mailing servers use without affecting its functionality? Also is it possible to reduce the amount of memory that the named process uses? Because named is using 76532k itself and I'm not sure if it's actually supposed to use that much.

 

[Crusader]

Those services would be running regardless of DirectAdmin. Getting rid of DA might not be a good idea if you don't know how to run a webserver

 

[animuson]

Yea that's what I'm getting at. This post has two questions in one. One was would everything still work on its own without DirectAdmin running and the second was how to optimize things to free up more virtual memory.

 

[nobaloney]

You can always shut down DirectAdmin and see if you can do everything you want to do. Then if you can you can, you can cancel the license.

Be sure to keep in mind that you'll need working shell access as you will no longer have the control panel access.

And that you'll lose the DirectAdmin ability to update everything with one command. You'll have to keep track of updates and find latest versions of software yourself.

All daemons are started by startup scripts on your server; they weren't installed by DirectAdmin. You can manage the startup scripts and/or the config files to manage how many of each daemon are run.

BIND (the named daemon) keeps all the zones in memory. Additionally if you're using it as a caching nameserver (you shouldn't be, but I didn't set up your server so I don't know if you are or not) it keeps all the domains you've ever looked up in memory, until their TTL expires.

There are many of use who could log into your server and do some optimization for you, but if you're looking for a command or two to run, I don't think you'll find it.

Jeff