New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 783117 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

wpa_supplicant starting too early during boot?

Project Member Reported by mnissler@chromium.org, Nov 9 2017

Issue description

A recent bootchart shows wpa_supplicant starting early: https://drive.google.com/open?id=1mMrr-K_9d5Mh95YG8UBOEkk0YWXijwNT

Indeed, wpasupplicant has "start on started boot-services". We should only be doing this for services that are required to bring up the UI, which doesn't seem the case for wpa_supplicant, thus potentially impacting boot performance negatively.

We should change wpasupplication.conf to "start on started system-services" or alternatively add documentation to wpasupplicant.conf that explains why we need it early and justifies the boot perf impact.

Assigning to cernekee@ for now since he is my best guest for the person who is most likely to have context.
 

Sign in to add a comment