Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FvwmMFL: make pid file slight more unique #365

Merged
merged 1 commit into from
Dec 20, 2020
Merged

Conversation

ThomasAdam
Copy link
Member

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.

@ThomasAdam ThomasAdam added this to the 1.0.2 milestone Dec 20, 2020
@ThomasAdam ThomasAdam self-assigned this Dec 20, 2020
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.
@ThomasAdam ThomasAdam merged commit 2a68510 into master Dec 20, 2020
@ThomasAdam ThomasAdam deleted the ta/fvwmml-displayname branch December 20, 2020 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant