Rather than depending on watershed, it would be better to detect when
we're invoked by cryptdisks_start and not require watershed at all.
Watershed is really only required when there's the possibility of two
processes trying to decrypt the same disk at the same time; while this
might happen with cryptdisks_start, that would be user error rather than
an init system bug, and it's probably simpler to not guard against this
case.
** Changed in: cryptsetup (Ubuntu)
Status: New => Triaged
--
dependancy problem: cryptdisks_start should require watershed
https://bugs.launchpad.net/bugs/656149
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
