> Uhm, so I should ENABLE the service, and then prevent it from starting?
You would be adding a condition for it to start. Native systemd services can have such conditions in the service definition file, but in xenial samba is not one of those I'm afraid. In fact, the samba package has a mess of 3 init systems config files in it in xenial: sysv, upstart and systemd. > Isn't that a bit convolute? It's not the most common scenario: only start the service if a certain mount point is in use? All that being said, it was my personal honest statement when I said i wasn't sure what the right outcome would be in such a case: service disabled, but running (started manually), and an upgrade comes along. It's excellent that you found these other packages which behave differently. Do they have native systemd service files, or are they using the sysv compatibility feature like samba is? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737534 Title: smbd/nmbd don't restart after upgrade if started but disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1737534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
