Bug#840608: systemd: nmbd.service long time to start when rebooting

Control: reassign -1 samba I didn't see anything which would point at an issue in systemd, so I'm reassigning this to the samba package. Your strace showed quite a bit of network activity, so maybe nmbd just takes a bit longer on initial startup under certain conditions. The samba maintainers can

Bug#840608: systemd: nmbd.service long time to start when rebooting

No difference between allow-hotplug auto directives in /etc/network/interfaces. On 10/17/16, Kirill Sutulo wrote: > this is nmbd strace output > > On 10/13/16, Michael Biebl wrote: >> Am 13.10.2016 um 15:33 schrieb Kirill Sutulo: >>> I can not find someone

Bug#840608: systemd: nmbd.service long time to start when rebooting

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 wrote: >> Yes.

Bug#840608: systemd: nmbd.service long time to start when rebooting

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? Thank You! On 10/13/16, Kirill Sutulo wrote: > Yes. restarting service is very fast. > > On 10/13/16, Michael Biebl

Bug#840608: systemd: nmbd.service long time to start when rebooting

Yes. restarting service is very fast. On 10/13/16, Michael Biebl 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 >>

Bug#840608: systemd: nmbd.service long time to start when rebooting

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