No difference between allow-hotplug auto directives in /etc/network/interfaces.
On 10/17/16, Kirill Sutulo <sut...@gmail.com> wrote: > this is nmbd strace output > > On 10/13/16, Michael Biebl <bi...@debian.org> wrote: >> Am 13.10.2016 um 15:33 schrieb Kirill Sutulo: >>> I can not find someone waiting for this service. The problem persists >>> also at the two VMs. >>> >>> Maybe strace log helps? Or reportbug to samba package? >> >> A strace would be helpful. >> >>> On 10/13/16, Kirill Sutulo <sut...@gmail.com> wrote: >>>> Yes. restarting service is very fast. >>>> >>>> On 10/13/16, Michael Biebl <bi...@debian.org> wrote: >>>>> Control: tags -1 + moreinfo >>>>> >>>>> Hi >>>>> Am 13.10.2016 um 10:33 schrieb kirill: >>>>> >>>>>> systemd-analyze blame | head -8 >>>>>> 22.026s nmbd.service >>>>>> 6.217s systemd-tmpfiles-setup.service >>>>>> 4.462s networking.service >>>>>> 3.521s alsa-restore.service >>>>>> 3.474s pppd-dns.service >>>>>> 3.473s incron.service >>>>>> 3.465s systemd-logind.service >>>>>> 3.456s rc-local.service >>>>>> --------------------------- >>>>>> systemd-analyze critical-chain >>>>>> >>>>>> graphical.target @36.509s >>>>>> └─multi-user.target @36.509s >>>>>> └─smbd.service @35.994s +514ms >>>>>> └─nmbd.service @13.967s +22.026s >>>>>> └─basic.target @13.946s >>>>>> └─paths.target @13.946s >>>>>> └─cups.path @13.946s >>>>>> └─sysinit.target @13.871s >>>>>> └─nfs-common.service @13.481s +389ms >>>>>> └─rpcbind.target @13.481s >>>>>> └─rpcbind.service @12.167s +1.313s >>>>>> └─network-online.target @12.167s >>>>>> └─network.target @12.167s >>>>>> └─ifup@eth0.service @12.167s >> >> If you change your network configuration in /etc/network/interface and >> you use "auto" instead of "allow-hotplug", does it make a difference? >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >