debugd starting too early? |
|||
Issue descriptiondebugd.conf currently says "start on started ui". This starts the service before we've reached the login screen, which I don't see a good reason for. We should either change the job to "start on started system-services" or if there is a good reason to start it early, document the reason in a comment in debugd.conf and justify any boot perf impact. Assigning to jorgelo@ per debugd/OWNERS
,
Nov 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/aosp/platform/system/tpm/+/38a7897b6f80bc4eee68ddfba499fec95218e217 commit 38a7897b6f80bc4eee68ddfba499fec95218e217 Author: Jorge Lucangeli Obes <jorgelo@chromium.org> Date: Tue Nov 14 18:11:20 2017 attestation: Use VPD cache. BUG=chromium:783127 TEST=PreCQ passes. Change-Id: I75a200f42bb7710e478e96c31fc02b07cc570fd8 Reviewed-on: https://chromium-review.googlesource.com/766587 Commit-Ready: Jorge Lucangeli Obes <jorgelo@chromium.org> Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Mattias Nissler <mnissler@chromium.org> Reviewed-by: Yves Arrouye <drcrash@chromium.org> [modify] https://crrev.com/38a7897b6f80bc4eee68ddfba499fec95218e217/attestation/server/attestationd.conf
,
Nov 14 2017
Oh man I used the wrong bug number.
,
Aug 1
,
Sep 18
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jorgelo@chromium.org
, Nov 9 2017