FvwmMFL: make pid file slight more unique #365
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When FvwmMFL learned to only start one instance of itself, the pid file
used didn't contain any unique attribute. As such, trying to run fvwm3
with FvwmMFL under Xephyr meant that separate instance of FvwmMFL was
never started.
To fix this, embed the DISPLAY value to the pid filename to allow it to
run more than once, albeit unique to each display.