| commit | b317e7506702c29d789c6e977b9a09f8130f3c27 | [log] [tgz] |
|---|---|---|
| author | Jae Hoon Kim <kimjae@chromium.org> | Thu Jun 16 23:12:06 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 08 08:48:41 2022 |
| tree | 9c6898b7171a510e293fca76fa23aedfe46b8e0f | |
| parent | dcfba1c5ea22985e0f2522bc5dc40b75945f6ce9 [diff] |
lvmd: Create LVM D-Bus daemon + exposing LV getters lvmd is a short live daemon that shuts down and is activated on demand when other processes/daemons require running LVM commands. There is no reason for lvmd to be up and running all the time and is more resourceful to shutdown as D-Bus activation can be used to transparently initialize lvmd when required. lvmd is also created to limit the root like permissions/selinux policies required to run LVM commands. Expose D-Bus getter methods to read into logical volume related information. BUG=b:236007986 TEST=emerge-$B lvmd lvmd-client chromeos-base/system-api TEST=dbus-send on org.chromium.Lvmd D-Bus interface Change-Id: Ie0b7879802c54db92969222ed0f7a26ee8f05c7a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3735890 Commit-Queue: Jae Hoon Kim <kimjae@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Sarthak Kukreti <sarthakkukreti@chromium.org> Tested-by: Jae Hoon Kim <kimjae@chromium.org> NOKEYCHECK=True GitOrigin-RevId: 6b1ae76648edea9613b94f5587296451515d5054
This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.
This directory is only for things like headers and .proto files. No implementation should be added.
When writting a .proto file make sure to use:
option optimize_for = LITE_RUNTIME;
This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.
When declaring a protobuf, avoid use of required unless it is exactly what you mean. “Required is Forever” and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.