... O cómo eliminar los Logs del SSD El problema principal de los SSD es que tiene un número de ciclos de lectura y escritura. El problema es que hay procesos como los LOGS que escriben en el disco, poca información, pero que constantemente producen la muerte prematura de nuestro precioso disco SSD. Entonces pensé en unirme a los dos mundos de las discotecas de SSD y HHD, para que hagan lo que mejor hacen. En mi servidor privado (un OrangePi PC2) está directamente conectado a Internet con una IP fija, config. IspConfig y estoy muy contento con su velocidad. Ahora estoy esperando que lleguen a las dos discotecas, un SSD y un HHD del mismo tamaño (120 GB) Mirando en el sistema de archivos hay muchos LOGS [SPOILER = "lista de registro"] root @ video: / # encontrar. -nombre "* .log" ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase-multiline.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase01.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase-journal.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase04.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase03.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase02.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/zzz-sshd-obsolete-multiline.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase-usedns.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase-wrong-char.log ./usr/lib/python3/dist-packages/fail2ban/tests/files/testcase01a.log ./usr/local/ispconfig/interface/temp/ids.log ./var/lib/mysql/tc.log ./var/www/clients/client1/web3/log/20190719-access.log ./var/www/clients/client1/web3/log/error.log ./var/www/clients/client1/web3/log/20190722-access.log ./var/www/clients/client1/web3/log/yesterday-access.log ./var/www/clients/client1/web3/log/access.log ./var/www/clients/client1/web2/log/20190719-access.log ./var/www/clients/client1/web2/log/error.log ./var/www/clients/client1/web2/log/20190722-access.log ./var/www/clients/client1/web2/log/20190718-access.log ./var/www/clients/client1/web2/log/20190720-access.log ./var/www/clients/client1/web2/log/20190723-access.log ./var/www/clients/client1/web2/log/yesterday-access.log ./var/www/clients/client1/web2/log/20190721-access.log ./var/www/clients/client1/web2/log/access.log ./var/www/clients/client0/web1/log/20190719-access.log ./var/www/clients/client0/web1/log/error.log ./var/www/clients/client0/web1/log/20190722-access.log ./var/www/clients/client0/web1/log/20190718-access.log ./var/www/clients/client0/web1/log/20190720-access.log ./var/www/clients/client0/web1/log/20190723-access.log ./var/www/clients/client0/web1/log/yesterday-access.log ./var/www/clients/client0/web1/log/20190721-access.log ./var/www/clients/client0/web1/log/access.log ./var/log/armbian-hardware-monitor.log ./var/log/dbconfig-common/dbc.log ./var/log/dpkg.log ./var/log/auth.log ./var/log/fontconfig.log ./var/log/rkhunter.log ./var/log/mysql/error.log ./var/log/mail.log ./var/log/kern.log ./var/log/apache2/access.log ./var/log/apache2/suexec.log ./var/log/apache2/other_vhosts_access.log ./var/log/apache2/error.log ./var/log/unattended-upgrades/unattended-upgrades-shutdown.log ./var/log/clamav/freshclam.log ./var/log/clamav/clamav.log ./var/log/ispconfig_config.log ./var/log/ispconfig/auth.log ./var/log/ispconfig/ispconfig.log .. ./var/log/ispconfig/cron.log ./var/log/apt/term.log ./var/log/apt/history.log ./var/log/bootstrap.log ./var/log/php7.2-fpm.log ./var/log/fail2ban.log ./var/log/ispconfig_install.log ./var/log/pure-ftpd/transfer.log ./var/log/nand-sata-install.log ./var/log/alternatives.log ./var/log/letsencrypt/letsencrypt.log ./var/log.hdd/alternatives.log ./var/log.hdd/nand-sata-install.log ./var/log.hdd/rkhunter.log ./var/log.hdd/fail2ban.log ./var/log.hdd/ispconfig/cron.log ./var/log.hdd/ispconfig/auth.log ./var/log.hdd/ispconfig/ispconfig.log ./var/log.hdd/apt/history.log ./var/log.hdd/apt/term.log ./var/log.hdd/ispconfig_install.log ./var/log.hdd/unattended-upgrades/unattended-upgrades-shutdown.log ./var/log.hdd/armbian-hardware-monitor.log ./var/log.hdd/dpkg.log ./var/log.hdd/mysql/error.log ./var/log.hdd/mail.log ./var/log.hdd/pure-ftpd/transfer.log ./var/log.hdd/clamav/clamav.log ./var/log.hdd/clamav/freshclam.log ./var/log.hdd/fontconfig.log ./var/log.hdd/bootstrap.log ./var/log.hdd/apache2/error.log ./var/log.hdd/apache2/other_vhosts_access.log ./var/log.hdd/apache2/suexec.log ./var/log.hdd/apache2/access.log ./var/log.hdd/kern.log ./var/log.hdd/armbian-ramlog.log ./var/log.hdd/dbconfig-common/dbc.log ./var/log.hdd/auth.log ./var/log.hdd/php7.2-fpm.log ./var/log.hdd/letsencrypt/letsencrypt.log ./var/log.hdd/ispconfig_config.log ./run/initramfs/fsck.log ./media/mmcboot/var/log/apt/term.log ./media/mmcboot/var/log/apt/history.log ./media/mmcboot/var/log/nand-sata-install.log ./media/mmcboot/var/log/dpkg.log ./media/mmcboot/var/log/armbian-hardware-monitor.log ./media/mmcboot/var/log/kern.log ./media/mmcboot/var/log/armbian-ramlog.log ./media/mmcboot/var/log/bootstrap.log ./media/mmcboot/var/log/alternatives.log ./media/mmcboot/var/log/auth.log ./media/mmcboot/var/log/unattended-upgrades/unattended-upgrades-shutdown.log raíz @ video: / # [/ SPOILER] Así es que pensamos en colocar el disco SSD como disco principal en / dev / sda1 y mantenerlo replicado en / dev / sdb1 (el disco HHD) con rsync. Pero lo más importante es que voy a reemplazar todos los archivos .log de / dev / sda1 con enlaces simbólicos a / dev / sdb1 De esta manera, el SSD casi siempre puede servir en la lectura y pocas escrituras (carga de archivos, nuevos registros de MariaDB y poco más) Mientras que los registros están físicamente todos en el HHD. Así que pensé en crear un script bash simple que se ejecute a través de todo el sistema de archivos en /, y si encuentra un .log que no sea un enlace simbólico, lo mueve a la unidad de disco duro y crea el enlace en su lugar Con rsync te puedo decir que no sincroniza los registros ¿Podría funcionar?
No. And the way you were searching for logs is wrong which lead you to wrong conclusions. All frequently written logs on your Linux system are in /var/log.E.g. all web server log files you found in /var/www are indeed the files from /var/log/ispconfig/httpd/.... as these are mounted via bind mounts. So all you have to do is to mount /var/log from a non-ssd drive, that's all.
Thank you very much for your comment, it has been a great help. I will do exactly as you tell me. Much more simple and effective.
