Keeping DirectAdmin servers maintained

[zaphod]

Hi All,

I was just wondering, what procedures are others following for keeping DirectAdmin servers updated?

We use yum for maintaining the rpm-based software on our DirectAdmin servers, and that works well, but for the source based packages is manually updating the build files and downloading the updated tarballs the only way to go about keeping httpd/php/etc updated when a newer version comes out? Once you get to a decent number of servers, doing things this way is at very least a pain and feels somewhat antiquated.

We also have some servers where we have customized build files (for extra modules with particular packages depending on the client's needs) and we need to redo these in the build files each time they are updated.

What are others doing to reduce the level of maintenance work involved in keeping their DA servers updated?

 

[nobaloney]

As you do, we use yum to update all the CentOS maintained packages.

Most internet-facing programs on the server are installed by DA and we update the entire customapache system from time to time.

We also use an outside service to monitor for daemons with holes in them and we update those that we must.

However, note that the latter doesn't work for RedHat distributed daemons using yum and RPMs because RedHat backports fixes to old version numbers, so most outside services will continue to warn you.

Jeff