Weird conntrackd / upstart interaction |
|||
Issue descriptionEvery so often, `start conntrackd` or `stop conntrackd` will hang. Not sure why. AFAIK, it does not affect normal Chrome OS operation, only development. This is not reproducible on demand. In particular, this test does not trigger the problem: while :; do start conntrackd; busybox usleep $RANDOM; stop conntrackd; busybox usleep $RANDOM; done
,
May 10 2018
posted https://chromium-review.googlesource.com/1053432
,
May 10 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/092185e6c13fc64d7dc5589946f5f2bc79d56b3c commit 092185e6c13fc64d7dc5589946f5f2bc79d56b3c Author: Mike Frysinger <vapier@chromium.org> Date: Thu May 10 22:09:59 2018 conntrack-tools: fix init tracking minijail0 & conntrackd both stay in the foreground, so "expect daemon" doesn't work as it expects a third process to fork and the others to exit. Add -i to minijail0 so that the first minijail0 exits, and change to "expect fork" so the conntrackd process is tracked by upstart. BUG= chromium:684014 TEST=start/stop works in a loop Change-Id: Ic3ed00fcb6ff447301a8f896da1a3545623c7ed9 Reviewed-on: https://chromium-review.googlesource.com/1053432 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Kevin Cernekee <cernekee@chromium.org> [modify] https://crrev.com/092185e6c13fc64d7dc5589946f5f2bc79d56b3c/net-firewall/conntrack-tools/files/init/conntrackd.conf [rename] https://crrev.com/092185e6c13fc64d7dc5589946f5f2bc79d56b3c/net-firewall/conntrack-tools/conntrack-tools-1.4.4-r6.ebuild
,
May 11 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by pauljensen@chromium.org
, Jan 23 2017