There is indeed a race in the upstart job, which makes it unable to
receive the kernel events. It works every time now after changing the
upstart job to start on 'started' instead of 'starting' udev.
Looking at the libudev code, this is what is currently happening:
"""
struct udev_monitor *udev_monitor_new_from_netlink_fd(struct udev *udev, const
char *name, int fd)
{
struct udev_monitor *udev_monitor;
unsigned int group;
if (udev == NULL)
return NULL;
if (name == NULL)
group = UDEV_MONITOR_NONE;
else if (streq(name, "udev")) {
/*
* We do not support subscribing to uevents if no instance of
* udev is running. Uevents would otherwise broadcast the
* processing data of the host into containers, which is not
* desired.
*
* Containers will currently not get any udev uevents, until
* a supporting infrastructure is available.
*
* We do not set a netlink multicast group here, so the socket
* will not receive any messages.
*/
if (access("/run/udev/control", F_OK) < 0 &&
!udev_has_devtmpfs(udev)) {
log_debug("the udev service seems not to be active,
disable the monitor");
group = UDEV_MONITOR_NONE;
} else
group = UDEV_MONITOR_UDEV;
} else if (streq(name, "kernel"))
group = UDEV_MONITOR_KERNEL;
else
return NULL;
....
"""
Added some debug lines in the upstart-udev-bridge job and
/run/udev/control is not necessarily available when this job starts (I'd
guess it only happens on ubuntu-touch, since we start udev a bit later
than the desktop).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412543
Title:
udev bridge fails to get events from kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1412543/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
