Updating leave old files behind.

Updating leave old files behind.

I have numerous servers running custombuild. We update these monthly.

After a few updates I seem to get quite alot of old installation folders for, among other things, mysql:

Code:

server:~# du -sh /usr/local/mysql*
0      /usr/local/mysql
487M    /usr/local/mysql-5.1.54-linux-x86_64
488M    /usr/local/mysql-5.1.55-linux-x86_64
130M    /usr/local/mysql-5.1.55-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.56-linux-x86_64
130M    /usr/local/mysql-5.1.56-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.57-linux-x86_64
130M    /usr/local/mysql-5.1.57-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.58-linux-x86_64
130M    /usr/local/mysql-5.1.58-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.59-linux-x86_64
130M    /usr/local/mysql-5.1.59-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.60-linux-x86_64
130M    /usr/local/mysql-5.1.60-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.61-linux-x86_64
130M    /usr/local/mysql-5.1.61-linux-x86_64.tar.gz
486M    /usr/local/mysql-5.1.62-linux-x86_64
130M    /usr/local/mysql-5.1.62-linux-x86_64.tar.gz
487M    /usr/local/mysql-5.1.63-linux-x86_64
130M    /usr/local/mysql-5.1.63-linux-x86_64.tar.gz
488M    /usr/local/mysql-5.1.65-linux-x86_64
130M    /usr/local/mysql-5.1.65-linux-x86_64.tar.gz


Is it fair to assume that only the folder with the highest version number (and the one pointed to by the mysql-symlink) is the one in use?

Is it safe to assume the older ones is just to delete?
What is the recommended way to do such "housekeeping"?

Comments are closed.