Correct RemainsAfterExit=true to be RemainAfterExit=true in nvidia.service #1169
Assignees
Labels
Comments
github-project-automation
bot
moved this to 📝 Needs Triage
in Flatcar tactical, release planning, and roadmap
pothos
moved this from 📝 Needs Triage
to 🌱 Upcoming / Focus
in Flatcar tactical, release planning, and roadmap
|
I've been working on the nvidia-drivers migration to latest version. I will fix it along with that PR. |
sayanchowdhury
added a commit
to flatcar/scripts
that referenced
this issue
Sep 8, 2023
Fixes flatcar/Flatcar#1169 Signed-off-by: Sayan Chowdhury <[email protected]>
2 tasks
dongsupark
moved this from 🌱 Upcoming / Focus
to ⚒️ In Progress
in Flatcar tactical, release planning, and roadmap
sayanchowdhury
added a commit
to flatcar/scripts
that referenced
this issue
Sep 8, 2023
Fixes flatcar/Flatcar#1169 Signed-off-by: Sayan Chowdhury <[email protected]>
github-project-automation
bot
moved this from ⚒️ In Progress
to Implemented
in Flatcar tactical, release planning, and roadmap
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In the new Alpha the unit setting
RemainsAfterExit=trueis ignored fornvidia.serviceand should be corrected toRemainAfterExit=truein/usr/lib/systemd/system/nvidia.serviceImpact
Maybe it's causing problems if the service runs again when triggered as dependency
The text was updated successfully, but these errors were encountered: