First pull for v1.7.2 #245
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s on bootup The idea to automatically stop an instance of this unit when the corresponding mounting unit is stopped, works as intended. Manually starting this unit or the corresponding mounting unit, also causes the other one to start, and stopping either one also stops the other one. But for some reason this does not work on boot-up: a. The udev rule starts an instance of this unlocking (opening) unit. b. This unit unlocks (opens) a Cryptsetup device. c. Another udev rule starts an corresponding instance of a mounting unit. d. I suspect that that unit (started in c.) enters temporarily a "failed" state, maybe because `udisks2.service` is not ready yet. e. What can be observed from the Systemd journal, is that Systemd stops the unlocking unit (from a.), which in turn also stops the corresponding mounting unit. Omitting `PartOf=mount-cryptosd-luks@%i.service` "fixes" this. Leaving it as a comment for now. Reference: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#PartOf=
…ls on bootup The idea to automatically stop an instance of this unit when the corresponding mounting unit is stopped, works as intended. Manually starting this unit or the corresponding mounting unit, also causes the other one to start, and stopping either one also stops the other one. But for some reason this does not work on boot-up: a. The udev rule starts an instance of this unlocking (opening) unit. b. This unit unlocks (opens) a Cryptsetup device. c. Another udev rule starts an corresponding instance of a mounting unit. d. I suspect that that unit (started in c.) enters temporarily a "failed" state, maybe because `udisks2.service` is not ready yet. e. What can be observed from the Systemd journal, is that Systemd stops the unlocking unit (from a.), which in turn also stops the corresponding mounting unit. Omitting `PartOf=mount-cryptosd-plain@%i.service` "fixes" this. Leaving it as a comment for now. Reference: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#PartOf=
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
First pull for v1.7.2