Config variable $nrconf{restart} is no longer accurate: it always restarts
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
needrestart (Ubuntu) | Status tracked in Oracular | |||||
Noble |
Fix Released
|
Undecided
|
Unassigned | |||
Oracular |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The normal configuration knob to change the behaviour of needrestart wrt restarting services vs asking the user vs just listing them doesn't work anymore on Noble due to the "Ubuntu mode" changes made during that cycle.
[Test plan]
echo '$nrconf{restart} = "l";' > /etc/needrestar
apt reinstall libc6
# The previous command should not have restarted any service.
[ Where problems could occur ]
If the patch is buggy, automatic restart could be disabled for all users. However, that use case is checked by the autopkgtests.
[Original report]
On Ubuntu 24.04:
The conf /etc/needrestar
# Restart mode: (l)ist only, (i)nteractive or (a)utomatically.
#
# ATTENTION: If needrestart is configured to run in interactive mode but is run
# non-interactive (i.e. unattended-
#
#$nrconf{restart} = 'i';
Whether that variable is left at default (commented out) or defined with 'l' or 'i', services are still restarted.
This config variable conflicts with the new behavior in [1].
To reproduce: set "$nrconf{restart} = 'l'" run 'apt reinstall libssl3t64' on servers with Nginx, Redis, etc.
Not sure if this setting should be respected, changed, or removed.
[1] https:/
Changed in needrestart (Ubuntu Oracular): | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Confirmed |
status: | Confirmed → Fix Committed |
description: | updated |
Changed in needrestart (Ubuntu Noble): | |
status: | New → In Progress |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.