Hello,
I searched but did not find any pointout's for issue we have.
http://www.directadmin.com/install.html
DA says that
/usr 5-12 gig. Just DA data, source code, frontpage.
But that's not true - when you do ./build mysql then mysql backs up it's data to /usr/local/directadmin/custombuild/mysql_backups
1. When there are large databases (larger than the partition), backing up db's and updating mysql fails;
2. Mysql install are usually 100+M and they are also stored in /usr/local/directadmin/scripts/packages forever and they have to be manually deleted.
And remember how often there is an update, what a waste of space.
Am I missing something or is it so?
Currently we have made a symlink for ../mysql_backups to partition where there is necessary space.
Note that this is the case when you use separate parititioning - /usr, /home, /tmp etc.
Regards,
HKI
I searched but did not find any pointout's for issue we have.
http://www.directadmin.com/install.html
DA says that
/usr 5-12 gig. Just DA data, source code, frontpage.
But that's not true - when you do ./build mysql then mysql backs up it's data to /usr/local/directadmin/custombuild/mysql_backups
1. When there are large databases (larger than the partition), backing up db's and updating mysql fails;
2. Mysql install are usually 100+M and they are also stored in /usr/local/directadmin/scripts/packages forever and they have to be manually deleted.
And remember how often there is an update, what a waste of space.
Am I missing something or is it so?
Currently we have made a symlink for ../mysql_backups to partition where there is necessary space.
Note that this is the case when you use separate parititioning - /usr, /home, /tmp etc.
Regards,
HKI
