Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about TeamsIt looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.
If you wish, you may also create a seperate directory owned and writeable myby the mysql user and specify that directory in my.cnf to be used instead of the system wide /tmp.
It looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.
If you wish, you may also create a seperate directory owned and writeable my the mysql user and specify that directory in my.cnf to be used instead of the system wide /tmp.
It looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.
If you wish, you may also create a seperate directory owned and writeable by the mysql user and specify that directory in my.cnf to be used instead of the system wide /tmp.
It looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.
If you wish, you may also create a seperate directory owned and writeable my the mysql user and specify that directory in my.cnf to be used instead of the system wide /tmp.
It looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.
It looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.
If you wish, you may also create a seperate directory owned and writeable my the mysql user and specify that directory in my.cnf to be used instead of the system wide /tmp.
It looks like your permissions on /tmp are wrong. They really should be read/write/execute for everyone with the sticky bit set.
chmod 1777 /tmp The sticky bit add some restrictions to how other users interact with files not created or owned by them, so there's no reason to worry.