Re: MySQL 8 UMASK change from 0666 to 0640
Posted by: Bjørn Munch
Date: March 15, 2023 04:09AM

That UMASK was changed for security reasons and you cannot change it back. So if your app does not have the right privileges, you will unfortunately have to adapt. You should be able to make a copy of the file which you can then modify.

Another possibility suggested in the reference manual: If your app can run the mysql client program, you can do mysql -e "SELECT ..." > file_name to generate the file. The app should then be able to modify the file, since it created it.

Options: ReplyQuote

Written By
Re: MySQL 8 UMASK change from 0666 to 0640
March 15, 2023 04:09AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.