[MXS-170] MaxScale doesnt support custom logging dir Created: 2015-05-25  Updated: 2015-06-09  Resolved: 2015-06-09

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.1.0
Fix Version/s: 1.2.0

Type: Bug Priority: Major
Reporter: Alexandros Biratsis Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: logging

Issue Links:
Duplicate
duplicates MXS-117 Allow configuration of the log file d... Closed

 Description   

MaxScale cant start when I set --log parameter. It seems that is not supported yet.

I receive the following when trying to set --log param

[devuser@ip-5-9-241-51 bin]$ ./maxscale --log=/tmp/maxscale/log

MariaDB Corporation MaxScale 1.1.0 Sun May 24 22:02:25 2015
------------------------------------------------------
*

  • Error : Configuration file argument identifier '-l' was specified but the argument didn't specify
    a valid configuration file or the argument was missing.
    *


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

markus makela Is this fixed in 1.1.1 already ?

Comment by markus makela [ 2015-06-09 ]

Closed as a duplicate of MXS-117

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