Open te-anhydros opened 3 months ago
The reason is that on dietpi-software
installs, services are stopped, so that the /var/log
tmpfs can be usually mounted without interrupting anything or being interrupted. On uninstalls, services are however not stopped, and some services keep their log files R/W open, so that trying to unmount the /var/log
tmpfs results in a "device is busy" error, or may crash the service.
However, I though already that we should just try it:
/var/log
content to disk/var/log
tmpfsHi @MichaIng, your counter-proposal is a more robust approach. I am all for it.
Do you have people on deck to implement this? If not, please direct me to the relevant files and functions and I'll try.
Thanks!
Sorry for the late reply. It is all in the dietpi-software
script: https://github.com/MichaIng/DietPi/blob/dev/dietpi/dietpi-software
Watch out for To_Uninstall 103
.
Creating a feature request
Is your feature request related to a problem? Please describe:
dietpi-software
to reconfigure logging from ramLog to fullLog, runningdf /var/log/.
showed that path to still be on a tmpfs.Describe the solution you'd like:
dietpi-software
manually, please add a prominent message to the module for managing/var/log
so that after a change from/var/log
being a tmpfs to being part of a regular filesystem telling the operator that the filesystem will change after the next reboot.dietpi-software
is running as part of the initial unattended install/update and the operator selects the fullLog option via/boot/dietpi.txt
, the process should add one more reboot to complete the process. That is what bit me today!Describe alternatives you've considered:
dietpi-software
having problems with this; found nothing.Additional context