[MDEV-16415] Make UMASK and UMASK_DEV configurable via server.cnf Created: 2018-06-06 Updated: 2019-07-15 Resolved: 2018-06-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Configuration, Server |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Thomas J. Girsch | Assignee: | Sergei Golubchik |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
In order to allow mariabackup to run under an ID other than "mysql" we need to create a backup ID and place it in the same group as mysql. However, when new databases are created, the directories and files are created without read/execute for the group ID. Thus, upon any new database creation, mariabackup starts failing. Currently, the only way to set UMASK_DIR on startup is to edit the service file, and these edits get overwritten any time an upgrade is installed. There's a way to set up an override file, but this type of configuration shouldn't be so esoteric. It should be as simple as setting the parameter in server.cnf, the way we do with most others. |
| Comments |
| Comment by Sergei Golubchik [ 2018-06-21 ] |
|
As far as server.cnf is concerned, it's a duplicate of MDEV-15844. But really, you don't need to wait for it, you can set variables from a service file that is not overwritten. In short, create a new file, say, umask.conf and put it in /etc/systemd/system/mariadb.service.d/ |