On Wed, 14 Oct 2015 05:45:05 -0700, Allyn Bottorff <abotto...@gmail.com> wrote:

Unless you use a service that actually provides it, a target will do absolutely nothing on its own. So how is using the proper things "not an ideal solution"?

Systemd's own networkd should provide that target.
It's not an ideal solution because using that service extends the boot
time in a way that shouldn't be necessary in this case. It forces the
boot to wait until the network is up and an IP address is assigned. Besides, it didn't solve the problem anyway, so this particular
discussion is academic.

Have you tried to reproduce this issue by disabling systemd's networkd and using Arch's netctl to configure the interface?

--
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org

Reply via email to