Skip to content

fix: find what runs in a symlinked bottle by what the link points at, because Stop killed only its wineserver - #23

Merged
typester merged 1 commit into
mainfrom
fix/symlinked-bottle
Oct 2, 2026
Merged

typester merged 1 commit into
mainfrom
fix/symlinked-bottle

Conversation

@typester

@typester typester commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Fixes #15.

… because Stop killed only its wineserver

Fixes #15.
@typester
typester merged commit 16cc4f2 into main Oct 2, 2026
2 checks passed
@typester
typester deleted the fix/symlinked-bottle branch October 2, 2026 03:54
typester pushed a commit that referenced this pull request Oct 5, 2026
🤖 I have created a release *beep* *boop*
---


## [0.2.1](v0.2.0...v0.2.1)
(2026-10-02)


### Bug Fixes

* find what runs in a symlinked bottle by what the link points at,
because Stop killed only its wineserver
([#23](#23))
([16cc4f2](16cc4f2))
* log what runs in each bottle to a directory of its own, because the
same title in two bottles shared one log
([#24](#24))
([ca8f5f7](ca8f5f7))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stop leaves a symlinked bottle running: serverDirectory reads the link, not the prefix

1 participant