I was quite surprised to see that by default, /var/lib/mysql and its database data is included in the CageFS skeleton. Per Mysql issues there appears to be a good reason for this (access to the MySQL socket required) but it still seems counter intuitive somehow, given the treatment of home, tmp, root and such.
I don't however know enough about the CageFS implementation details to know whether this matters enough that it's worth doing something about, so two questions:
1. Are the database files less protected being linked within the cage, even though the directory has permissions such that they cannot be read, than they would be if they were not included?
2. If the above = true, what would be the method to resolve the issue (move the socket) that would not break cPanel MySQL maintenance?
I don't however know enough about the CageFS implementation details to know whether this matters enough that it's worth doing something about, so two questions:
1. Are the database files less protected being linked within the cage, even though the directory has permissions such that they cannot be read, than they would be if they were not included?
2. If the above = true, what would be the method to resolve the issue (move the socket) that would not break cPanel MySQL maintenance?