"a stop job is running" for samba unmount

Clearly, there’s a sequence of events at system startup and, for example, some processes will need a network connection before starting. Systemd has complicated the picture a little because it can run things in parallel, giving the potential for “race conditions” to occur. As a result, systemd gives us the ability to control startup sequence with After=, Before=, Wants=, Requires= and so on.

So I guess the answer to your question “Is that correct?” is yes, since you’ve (re)defined a startup sequence that better meets your set-up.

The solution to modify connman.service does not seem to work anymore with the latest firmware. Is there another way to get rid of the “stop job is running” for the samba unmount?