Github user achristianson commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/242#discussion_r161790548
--- Diff: README.md ---
@@ -609,6 +609,21 @@ Additionally, a unique hexadecimal
uid.minifi.device.segment should be assigned
class: ControllerServiceClass
Properties:
+### Linux Power Manager Controller Service
+ The linux power manager controller service can be configured to monitor
the battery level and status ( discharging or charging ) via the following
configuration.
+ Simply provide the capacity path and status path along with your
threshold for the trigger and low battery alarm and you can monitor your
battery and throttle
+ the threadpools within MiNiFi C++. Note that the name is identified must
be ThreadPoolManager.
+
+ Controller Services:
+ - name: ThreadPoolManager
+ id: 2438e3c8-015a-1000-79ca-83af40ec1888
+ class: LinuxPowerManagerService
+ Properties:
+ Battery Capacity Path: /path/to/battery/capacity
+ Battery Status Path: /path/to/battery/status
--- End diff --
Is it feasible to detect these paths automatically if they aren't specified
by the user? I.e. use heuristics to check some standard locations, but still
allow the user to override if they're set manually.
---
