Vesta 2.0 is coming soon! See our progress update: https://vestacp.com/docs/vesta-2-update
Vestcp install fails if /tmp is mounted with noexec
Vestcp install fails if /tmp is mounted with noexec
Hi,
On Centos7.x usually, I mount /tmp with noexec for security reasons.
But, vesta installation fails saying /tmp can not have noexec. Why?
I created a temporary folder /tmpx and modified installer script and install went on successfully. After install, is the /tmpx is necessary for vesta operation? or I can remove it?
Thanks.
On Centos7.x usually, I mount /tmp with noexec for security reasons.
But, vesta installation fails saying /tmp can not have noexec. Why?
I created a temporary folder /tmpx and modified installer script and install went on successfully. After install, is the /tmpx is necessary for vesta operation? or I can remove it?
Thanks.
Re: Vestcp install fails if /tmp is mounted with noexec
For what you say have you done it right? so if it works for you, you can keep it without problem, VestaCP is updated very slowly and it may take time to integrate things that are needed.
Re: Vestcp install fails if /tmp is mounted with noexec
Thanks.
But, after install is the /tmpx folder created for install is needed for vesta regular operation? Or I can delete it safely?
But, after install is the /tmpx folder created for install is needed for vesta regular operation? Or I can delete it safely?
Re: Vestcp install fails if /tmp is mounted with noexec
I have not seen before VestaCP has created that folder, it must only exist /tmp and within this tmp.X
Re: Vestcp install fails if /tmp is mounted with noexec
No. /tmpx is not created by vesta. I created it for installing vest as specified in first post.
Re: Vestcp install fails if /tmp is mounted with noexec
The installation must remove it, because nothing is usually left in /
Re: Vestcp install fails if /tmp is mounted with noexec
Sorry.. I'm confused as I'm experimenting with lots of panels at a time.
This is an issue with virtualmin and NOT vestacp.
Great community here.
Thank you all.
This is an issue with virtualmin and NOT vestacp.
Great community here.
Thank you all.