Over on the Linux side, I installed Vanilla OS recently and it has a Samba service (nmbd.service) as a bootup dependency, which waits for a non-loopback IPv4 interface to be available. So if you're on a laptop which is not connected to WiFi, it will just hang for 90 seconds on the bootup screen before systemd decides that service has failed to start and moves on
Comments
Over on the Linux side, I installed Vanilla OS recently and it has a Samba service (nmbd.service) as a bootup dependency, which waits for a non-loopback IPv4 interface to be available. So if you're on a laptop which is not connected to WiFi, it will just hang for 90 seconds on the bootup screen before systemd decides that service has failed to start and moves on
It's a classic. I haven't played around with Samba in a long time, but if I remember correctly, you can either:
- configure SMB with a shorter timeout at boot
- configure your Samba share to mount with automount. (See [1] for inspiration)
[1] https://forum.manjaro.org/t/root-tip-how-to-systemd-mount-un...
I never understood why it waits so long, surely maybe 2-3 seconds would be plenty as a default.
You're in good hands.