Adopting as the upstream upstart bug for this problem
** Description changed:
- Binary package hint: mountall
+ Event operators are reset each time they become TRUE, with the blocking
+ state being transferred to the actual instance that is started. This
+ means that combining the two operators leads to undesirable behaviour.
- The latest upload of mountall fixed a typo in the "fhs" list ("/srv"
- "/sys" -> "/srv", "/sys"), and now my system hangs on boot. /srv is an
- NFSv4 filesystem on my machine, which means upstart now won't even enter
- runlevel 2 until it succeeds in mounting this filesystem... which it
- doesn't manage to do, for reasons I've so far been unable to discern.
- Instead, I get a hang in the ifupdown upstart script, waiting for
- 'initctl emit net-device-up IFACE=lo' to return.
+ For example, in /etc/init/quest.conf:
- I appear to get the same hang if another, non-fhs nfs4 mount is enabled
- for automounting in my fstab. So it looks like nfs4 support in general
- has somehow regressed with this upload; I'm continuing to investigate.
+ start on gandalf and (bilbo or thorin)
- ProblemType: Bug
- Architecture: amd64
- Date: Fri Oct 9 16:18:28 2009
- DistroRelease: Ubuntu 9.10
- Package: mountall 0.2.0
- ProcEnviron:
- PATH=(custom, user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
- ProcVersionSignature: Ubuntu 2.6.31-13.42-generic
- SourcePackage: mountall
- Uname: Linux 2.6.31-13-generic x86_64
+ When gandalf arrives, he'll block waiting for bilbo or thorin. If bilbo
+ then arrives, the operator tree is complete and the quest can start.
+
+ If thorin then arrives, he'll block waiting for gandalf. Unfortunately
+ gandalf has already gone, so he has little choice but to sit down and
+ start singing about gold.
+
+ A short-term fix is not to combine event operators this way, and instead
+ separate them out into separate jobs. For example if we had an
+ /etc/init/quest/member.conf with:
+
+ start on bilbo or thorin
+
+ Then /etc/init/quest.conf would have:
+
+ start on gandalf and started quest/member
+
+ In this case when gandalf arrives, he'd still block on a quest member.
+ Bilbo then arrives, "starting" the quest/member job and thus also
+ starting the quest.
+
+ If thorn then arrives, the quest/member job has already been started so
+ he doesn't block waiting for it to start.
+
+ The longer term fix is included in the move to "while", which means that
+ we'd remember that we had gandalf so when thorin arrived he'd know the
+ quest was already started - and he could either start a new quest or
+ catch up with the existing one.
--
init: using 'and' and 'or' operators together causes hangs
https://bugs.launchpad.net/bugs/447654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
