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

Issue 770150 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Emit 'policy-updated' signal when the device policies are created or changed

Reported by vpalatin@chromium.org, Sep 29 2017

Issue description

As mentioned in CL 617462 [1], it would nice to emit a signal when the device policies (in /var/lib/whitelist/policy) are created or updated, so other userspace components using libpolicy can start or reload their configuration.


[1] https://chromium-review.googlesource.com/c/chromiumos/platform2/+/617462
 

Comment 1 by derat@chromium.org, Sep 29 2017

Cc: mnissler@chromium.org
Components: Enterprise
Cc: emaxx@chromium.org
Labels: Enterprise-Triaged
Is this still relevant? The alternative approach with listening to the D-Bus signal should be sufficient in most cases, and it may give greater flexibility as one may implement any complex logic around those events (for example, whether only admin-controlled settings are observed or the owner-user settings on an unenrolled device too).
I haven't heard anything about this in the year it was filed, but I think that the original reason for this (per the CL above) was to make it possible to start an Upstart job. I don't think that D-Bus signal helps there.

Sign in to add a comment