touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

@Oli: timesyncd is part of systemd, and it doesn't need any integration
with ifupdown. It listens for coming and going network connections by
itself and adjusts its wakeups according to network availability and
precision of the clock. I specifically enabled this because the snappy
team asked me to :-)

@Victor: indeed, so everything which is "auto" in
/etc/network/interfaces/* is required for a complete boot. But I'm still
confused why it's blocking network.target. What kind of install is that,
standard snappy image on some laptop or beagle board or so? I'll try to
reproduce that in a snappy VM.

Anyway, I'm off to holidays for the next 1.5 weeks, so I'm setting that
to NEW for now. Thank you so far!

** Changed in: systemd (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431836

Title:
  Boot process takes too long when Ethernet is not connected

Status in Snappy Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  The boot process takes a minute with Internet access (e.g.: Ethernet)
  and several minutes when no Ethernet is connected. The kernel dump for
  the later is shown at
  https://gist.github.com/vmayoral/135aef30218b8d00d4f1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy-ubuntu/+bug/1431836/+subscriptions