numad doesn't respect settings in /etc/default/numad
Bug #1640783 reported by
geert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
numad (Debian) |
Fix Released
|
Unknown
|
|||
numad (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The systemd script for numad doesn't respect the settings in /etc/default/numad. The following changes make it work:
--- /lib/systemd/
+++ /root/numad_new 2016-11-10 14:00:54.502547863 +0100
@@ -3,10 +3,10 @@
Documentation=
[Service]
+EnvironmentFil
Type=forking
-ExecStart=
+ExecStart=
[Install]
WantedBy=
Changed in numad (Debian): | |
status: | Unknown → Fix Released |
Changed in numad (Ubuntu): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Hi geert,
Thank you for taking the time to report this bug and helping to make Ubuntu better.
I agree to your finding and solution. But This bug is present in Debian too, and Ubuntu currently doesn't make any changes over the Debian package. So this bug would be best fixed directly in Debian, and then Ubuntu will pick up the fix automatically.
Would you mind filing a bug with Debian please and link it here so that we can pick it up once accepted?