This has been fixed since 0.3.5 was uploaded into Ubuntu
** Changed in: upstart (Ubuntu)
Status: In Progress = Fix Released
--
does not read /etc/event.d if inotify unavailable
https://launchpad.net/bugs/68904
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: upstart (Ubuntu)
Status: Confirmed = In Progress
--
does not read /etc/event.d if inotify unavailable
https://launchpad.net/bugs/68904
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Release in 0.3.2
** Changed in: upstart (upstream)
Status: Fix Committed = Fix Released
--
does not read /etc/event.d if inotify unavailable
https://launchpad.net/bugs/68904
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Committed in rev 383
** Changed in: upstart (upstream)
Status: Confirmed = Fix Committed
--
does not read /etc/event.d if inotify unavailable
https://launchpad.net/bugs/68904
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Just a note to say that I was also bitten by this issue while trying to
set up an Edgy Xen domU. Since my dom0 is not Ubuntu, and all the other
(working) domUs use the same non-Ubuntu kernel, I did not immediately
suspect the kernel.
In fact I spent several hours googling around, setting --debug
Hi James, you are not alone anymore :-D.
I had the same problem, but in different situation (not doing an
upgrade). I used init with option -v and it reported ( I don't know if
it helps, Scott):
init: Reading configuration from /etc/event.d
But, it hangs after this message and scripts in
** Changed in: upstart (Ubuntu)
Status: Rejected = Confirmed
** Changed in: upstart (upstream)
Target: None = 0.3
--
does not read /etc/event.d if inotify unavailable
https://launchpad.net/bugs/68904
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
