I have configured Samba to run as an Active Directory Controller as per the Wiki page. After upgrading to version 4.13.0, systemd fails to start samba.service. When manually starting with command 'systemd start samba', I can see that all the processes are launched and for a brief moment Samba is working normally and responding to requests, but systemd doesn't think Samba has started and eventually gives up with a time out. Systemd then kills all the Samba processes that were started.It appears that Samba 4.13.0 doesn't work with the 'notify' service type. I have created a drop-in conf file '/etc/systemd/system/samba.service.d/samba.conf' to override the type to 'exec' like so:
Whilst probably not a perfect fix, this fixes the problem for me.
]]>