[MXS-58] MaxScale should put its files in normal locations on the filesystem Created: 2015-03-26  Updated: 2017-12-01  Resolved: 2015-08-26

Status: Closed
Project: MariaDB MaxScale
Component/s: Core, Packaging
Affects Version/s: None
Fix Version/s: 1.2.0

Type: New Feature Priority: Major
Reporter: Kolbe Kegel (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 1
Labels: None


 Description   

MaxScale installs in its own directory in /usr/local/. This is not normal behavior for packages. Instead, files should be put into the appropriate existing locations on the filesystem. For example, files should go to /etc/ instead of /usr/local/mariadb-maxscale/etc and /usr/bin instead of /usr/local/mariadb-maxscale/bin/.

It's annoying to have to set up custom PATH components to easily find the maxadmin executable, and it's strange not to be able to create a MaxScale.cnf file in /etc/. Logs should go to /var/log/maxscale so that they can be found easily.



 Comments   
Comment by markus makela [ 2015-05-10 ]

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

Comment by Dipti Joshi (Inactive) [ 2015-06-02 ]

markus makela Any documentation we need for this ?

Can you link the updated doc here?

Comment by markus makela [ 2015-06-03 ]

MaxScale startup:
https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Getting-Started/Getting-Started-With-MaxScale.md
https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Tutorials/Administration-Tutorial.md#starting

Library load paths:
https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Getting-Started/Configuration-Guide.md#protocol-modules

Configuration file:
https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Getting-Started/Configuration-Guide.md

Generated at Thu Feb 08 03:56:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.