Johan Wikman a0f905bbe9 Make maxscaled upgrade friendlier
Currently, if the address/port information of a maxscaled protocol
listener is not updated to socket when MaxScale is upgraded to 2.0,
maxscaled would not start, with the effect of a user loosing maxadmin
after an upgrade.

After this change, if address/port information is detected, a warning
is logged and the default socket path is used. That way, maxadmin will
still be usable after an upgrade, even if the address/port information
is not updated.
2016-08-24 14:00:19 +03:00
..
2016-08-11 12:44:07 +03:00
2016-08-11 12:44:07 +03:00
2016-08-24 14:00:19 +03:00
2016-08-11 12:44:07 +03:00
2016-08-11 12:44:07 +03:00