hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-1479 By default, refuse to run as root

Browse Source 
MaxScale now refuses to run as root. However, it is possible to
start MaxScale as root, as long as a user to run MaxScale as is
provided as a command line argument.

It is possible to run as root by invoking MaxScale as root and
by specifying the MaxScale user to be root.
This commit is contained in:
Johan Wikman
2017-11-08 14:46:08 +02:00
parent 42d9064b04
commit 0558a2195d
3 changed files with 65 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
Documentation/Release-Notes/MaxScale-2.2.1-Release-Notes.md
View File

@ -10,6 +10,21 @@ report at [Jira](https://jira.mariadb.org).
## Changed Features
### Process identity
By default, MaxScale can no longer be run as `root`, but must be run as some
other user. However, it is possible to start MaxScale as `root`, as long as
the user to run MaxScale as is provided as a command line argument:
```
root@host:~# maxscale --user=maxuser ...
```
If it is imperative to run MaxScale as root, e.g. in a Docker container, it
can be achieved by invoking MaxScale as root and by explicitly specifying
the user to also be root:
```
root@host:~# maxscale --user=root ...
```
### Binlog server
* The `mariadb10_slave_gtid` parameter was removed and slave connections can now