Does CentOS utilize the /tmp directory a lot when doing upgrades?
Posted: 2020/09/03 16:04:32
This is kind of a high level question
I've often found when doing version upgrades in CentOS 7, i.e. like when going from CentOS 7.6 to 7.7, or from 7.7 to 7.8, the updated system often becomes flaky and unstable. I've posted questions on this forum before when it happens, but I suspect because the issues are kind of vague and idiosyncratic, nobody has been able to suggest what the problem might be.
One thought occurred to me - one of the required security settings we have to implement is to set the noxec, nosuid, and nodev options when mounting the /tmp drive. During an upgrade is the operating system using the /tmp drive a lot as its doing the upgrade? Which, if the operating systems is assuming it has certain privileges/rights on the /tmp drive and it actually doesn't, would lead to things not installing correctly?
I've often found when doing version upgrades in CentOS 7, i.e. like when going from CentOS 7.6 to 7.7, or from 7.7 to 7.8, the updated system often becomes flaky and unstable. I've posted questions on this forum before when it happens, but I suspect because the issues are kind of vague and idiosyncratic, nobody has been able to suggest what the problem might be.
One thought occurred to me - one of the required security settings we have to implement is to set the noxec, nosuid, and nodev options when mounting the /tmp drive. During an upgrade is the operating system using the /tmp drive a lot as its doing the upgrade? Which, if the operating systems is assuming it has certain privileges/rights on the /tmp drive and it actually doesn't, would lead to things not installing correctly?