Comment 7 for bug 2059337

Just to recap some thoughts from the conversation cloud-init devs just had:

- Automatically killing non-interactive processes may have far-reaching changes. It may leave many packages besides cloud-init exposed. Any service that calls `apt upgrade` etc non-interactively may get killed. How confident do we feel that we'll catch them all before the noble release?
- One possible workaround in needrestart for this issue would be to automatically include its own parent PID in the list of ignored processes.
- If we do decide to keep the needsrestart patch as-is, cloud-init should really include all of its own services in the ignore list - cloud-init is not a long-running process and never wants to be restarted.