Added fallback path

[papafe]

Added new config parameter for the fallback path where named pipes used by realm should be created.

Fixes #2751

TODO

• Changelog entry

[peppy]

Since the configuration property has Fallback in its name, does this imply it will only be used in cases that creation beside the realm file fails?

One potential use case I have is wanting to always create the pipe files in a specified temporary folder to avoid compatibility issues (specifically, if a Parallels Desktop VM sees the pipe file it will seize up and require a kill -9 of the VM to recover - can be quite detrimental when a realm file is created in my home directory for whatever reason).

[papafe]

@peppy I agree the name is misleading, but actually if set it is used all the time.

[peppy]

Thanks for confirmation and for the implementation. Should help us heaps.

[smoogipoo]

Hi, I'm not sure that this is working on Linux (5.10.79-1-MANJARO). #2766 (comment) indicates that it should have an effect at all times if I understand correctly, though it still seems to create the pipe file in the original path.

We're choosing the path as follows (I've tested both as directory and as file):

string tempPathLocation = Path.Combine(Path.GetTempPath(), @"lazer");
if (!Directory.Exists(tempPathLocation))
    Directory.CreateDirectory(tempPathLocation);

As a side note, what is the expectation of the path value? A directory as I have above, or a file?

[papafe]

@smoogipoo I am really sorry, I gave you the wrong information because I misunderstood a piece of code. As you've noticed that path is being used only if it's not possible to create the pipe next to the realm file.

As an additional note, the fallback path should just be a directory, no need to point to a file, and should have a trailing slash