Comment 3 for bug 1321369

I've seen multiple reports involving the "samba", "smbd" and "nmbd" services, confusion in their behavior for starting, stopping, restarting, reloading etc, and in interaction between upstart jobs, init.d scripts and the "service" command.

I think these all have the same root cause, which stems from the "samba" init.d script having started two daemons in the past, that are now managed by separate upstart jobs, and users expectations that a single "samba" restart will suffice. This may be entirely reasonable, but currently this expectation seems to be broken in certain cases, leading to these reports.

So I'm marking the other bugs as duplicates as this one.