RDKEMW-22632: Order service start after PowerManager - #327
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a systemd drop-in to ensure wpeframework-networkmanager.service is ordered after wpeframework-powermanager.service, so PowerManager is started first on boot in GNOME-enabled builds.
Changes:
- Add a systemd drop-in setting
After=andWants=forwpeframework-powermanager.service. - Install the new drop-in into
wpeframework-networkmanager.service.dvia the plugin CMake install rules.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
plugin/gnome/systemd/gnome-powermanager-dependency.conf |
Introduces the systemd unit drop-in to order NetworkManager after PowerManager and pull it in. |
plugin/CMakeLists.txt |
Installs the new drop-in alongside existing NetworkManager systemd drop-ins when ENABLE_GNOME_NETWORKMANAGER is enabled. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
6add70f to
e0485e4
Compare
e0485e4 to
6fa89ab
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
plugin/gnome/systemd/gnome-powermanager-dependency.conf:3
After=only enforces ordering when both units are already part of the same transaction; it does not ensurewpeframework-powermanager.serviceis started. If the goal is to ensure PowerManager is started before NetworkManager, add a dependency likeWants=(orRequires=if NetworkManager cannot function without it) alongsideAfter=.
[Unit]
# Ensure NetworkManager starts after PowerManager
After=wpeframework-powermanager.service
6fa89ab to
ecb654a
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (1)
plugin/gnome/systemd/gnome-powermanager-dependency.conf:3
After=only enforces ordering if both units are started; it does not pull in/activate PowerManager. If the goal is to ensure PowerManager is started before this service, add a dependency (e.g.,Wants=orRequires=) alongsideAfter=so systemd will start PowerManager when NetworkManager is started.
[Unit]
# Ensure NetworkManager starts after PowerManager
After=wpeframework-powermanager.service
Reason for change: Ensure PowerManager service is started before NetworkManager Test procedure: Reboot, then inspect the order units actually started Risks: low Priority: P1 Signed-off-by: Anand N <Anand_N@comcast.com>
ecb654a to
3f3c55f
Compare
| [Unit] | ||
| # Ensure NetworkManager starts after PowerManager | ||
| After=wpeframework-powermanager.service |
Reason for change: Ensure PowerManager service is started before NetworkManager
Test procedure: Reboot, then inspect the order units actually started
Risks: low
Priority: P1