Bug #78808 Manual is wrong when explaining the default UMASK value
| Submitted: | 12 Oct 2015 16:57 | Modified: | 11 Dec 2015 18:41 |
|---|---|---|---|
| Reporter: | Valeriy Kravchuk | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 5.7 | OS: | Any |
| Assigned to: | Paul DuBois | CPU Architecture: | Any |
| Tags: | umask | ||
[12 Oct 2015 16:57]
Valeriy Kravchuk
[12 Oct 2015 20:26]
MySQL Verification Team
Thank you for the bug report.
[11 Dec 2015 18:41]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly. I've updated the 5.7 manual with the correct default UMASK/UMASK_DIR values (0640 and 0750 as of 5.7.6). I did not have problems changing the default permissions as described in the manual, *except* that, in attempting to follow the instructions at http://dev.mysql.com/doc/refman/5.7/en/file-permissions.html I found that I had to specify the values in octal. See: Bug #79608 mysqld_safe mishandles UMASK Since directory permissions are set as a combination of UMASK_DIR and UMASK, having mysqld_safe mishandle UMASK causes problems changing the default directory permissions. Perhaps you encountered a similar problem.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
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.