I've noticed after CyberPanel update to a recent version that upgrade.py script created a file /usr/.tempdisk of 1.5G for loop mount on /tmp, /var/tmp.
Can I ask the reasons behind this?
Is it safe to revert that change back to casual fs or at least change its size?
Comments
If you can configure /tmp on tmpfs its fine. But normally by default it may not be good, not everyone will have small /tmp and large ram.
You can customize /tmp to your needs, our main goal was to make temp noexec.
my disk space is critical now.
i already read "/tmp is now mounted with noexec,nosuid,nodev,nofail flags by default." but still doesn't understand what is the usage?
If wish to keep on disk but less in size, do the following:
1. Stop all your services (mariadb, litespeed, etc).
2. umount /var/tmp && umount /tmp
3. rm /usr/.tempdisk
4. dd if=/dev/zero of=/usr/.tempdisk bs=1M count=XX (where XX are wanted size in Mb)
5. mkfs.ext4 /usr/.tempdisk
6. Reboot
I can also use this to increase the /tmp partition?
Mine if 1.5GB (the default size) and I'm constantly getting core dumps in it so I have to delete those so that /tmp doesn't run out of space.
Could you explain why should I(we) set block size so 1M?