The current implementation of this change is in the install_dir_change branch on GitHub.

binlog dir is defined by option in maxscale.cnf. I will take care of binlog dir in my tests, but we need:

1. add note to the documentation that binlog directory have to be readable and writable by 'maxscale' user (probably here https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md#binlogdir)

2. take care of binlog directory during upgrade process: i'm not sure what should we do here - just change access rights or move files and how can upgrade script find binlog dir (need to parse .cnf??)

For what it's worth I don't run maxscale as root. I run it by default as a user maxscale.

The binlogdir is by default the same as the service directory unless explicitly configured as a router option. (I configure it as an explicit router option so I can specify where the binlog directory resides.) This directory is already readable and writeable by this user, so the only thing I will need to do is remove my own wrapper which change maxscale to be run as "maxscale" to use the new mechanism for this.

What's probably a good idea however, is for MaxScale's binlog router to check on start up if the binlogdir is readable and also writable and if it's not to basically give an error that permissions are wrong etc and point to what the cause might be. If the process is running as root then point to the fact that this is not now expected. If the binlogdirectory is owned by root and maxscale is running as another user then don't fix this but state what the problem is and that probably the binlog directory ownership needs to be changed. If the error message is clear then this should not be problematic.

markus makela Which user documentation needs to be updated for this feature ?

Hi,

Installed maxscale 1.2.0 on debian 7.8.

The init script contains, on line 48 (no quotes):

DAEMON_OPTS= --user=maxscale

Which leads to a warning at startup:

/etc/init.d/maxscale: line 48: --user=maxscale: command not found

I put single quotes, no more error at startup, but still I see it is running as root:

root@server:~# ps auxwwf |grep maxscale

root     17329  0.1  0.1 586720 51392 ?        Ssl  14:06   0:17 /usr/bin/maxscale  --user=maxscale

Joffrey

joffrey Please open a new bug for this.

Thanks,
Dipti