Comment 15 for bug 1792400

Tested an upgrade from proposed.
- upgrade worked
- Primary on trusty the upstart jobs are important which are not affected
- If I force execution of the sysV code (hacky) I'm affected and the proposed change from proposed fixes it
- So that isn't an issue for the majority of users, but still an issue since the same code is delivered. Looking back we might have skipped it on Trusty entirely, but it is not "wrong" to fix it
- on the positive side we also have not heard an issue on Xenial which got the same change recently.

Setting verified.

Example showing that the default upstart isn't affected:

ubuntu@T-smb-nested:~$ ps axlf | grep smbd
0 1000 13315 3315 20 0 10504 892 pipe_w S+ pts/0 0:00 | \_ grep --color=auto smbd
0 165536 13311 13204 20 0 7604 576 - S pts/6 0:00 \_ /usr/sbin/smbd 1h
4 0 13291 1 20 0 316760 9108 - Ss ? 0:00 smbd -F
1 0 13300 13291 20 0 308676 2840 - S ? 0:00 \_ smbd -F
1 0 13302 13291 20 0 316760 3080 - S ? 0:00 \_ smbd -F

$ sudo service smbd status; echo ""; sudo service smbd restart; echo ""; sudo service smbd status
smbd start/running, process 13291

smbd stop/waiting
smbd start/running, process 13334

smbd start/running, process 13334

So as I outlined before, not that impacted on Trusty, but for the sake of fixing code that the packages deliver pushing the fix is still correct.

If the SRU Team disagrees we could as well cancel the SRU at this stage and remove it from proposed - sorry for the noise then.