mlogger misleading crash if MIDAS_SERVER_HOST is set

[dd1]

we have a problem report. mlogger crashes in assert “_path_name.length() != 0” because cm_set_path() was not called because mlogger is trying to run remotely. we should print a better error message when this happens. K.O.

[Stefan Ritt]

The logge should NOT run remotely, since the performance would be miserable. MIDAS buffers are optimized for fast remote writing and fast local reading, but not for fast remote reading. We simply should exit the logger if one tries to start it remotely. Maybe just ignore MIDAS_SERVER_HOST for mlogger.