Hello, To set up quite speedy and spacy servers, I had the idea to : ' mount /dev/sd"SSD" / '==> to have an SSD for OS including basically /var Moreover, I saw that, I can mount bind partition : https://www.howtoforge.com/use_moun...ctory_of_a_ispconfig_server_to_a_new_location My idea is to mount --bind /var/vmail, and, systematically mount --bind /var/www/*/*/web*/private /sd_HDD/web*/private (with obviously a dedicated adequate line for each pathfile -> in text * are to simplify) the mount bind target partition would be an HDD. This would help combined speed (SSD) and space (HDD) : quite complex but manageable with a script. I have several questions : - Is this compatible with immutable bit on /var/www/*/*/web*/private. Do I have to remove before mount ? Can I put it back after ? - Is this compatible with quota. I read that https://www.howtoforge.com/community/threads/quota-combined-for-multiple-drives-devices.82624/ and understood that it should count per drive... What will appears in ISP Config dashboard : Many thanks
ISPConfig doesn't set immutable attribute on the private directory. If you did that yourself, I suspect you'll have to make it mutable prior to mounting/unmounting. (I don't know the answer on quota without testing it.)
My mistake on immutable bit ! Before writting, I should have 'lsattr' my dir ! it was too early... Digging a little bit, I see that in /var/www/clients/clientx/weby, all directories are not weby:clientx, some a root:root. Is it mandatory, can I do : chown -R weby:clientx /var/www/clients/clientx/weby
It's a bad idea security-wise (especially if you have hardlinked jailkit files, you will change the ownership of the actual system libraries/binaries/etc.). Why is it you think that would be a good thing to do, or is in any way a problem as is?
Scripting speaking, it is simplier... But, I thought there is probably a reason to have root:root, that's why I ask... Many thanks
