All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11731] New: buildroot 2019.02 systemd - long start Network name resolution service
Date: Thu, 21 Mar 2019 09:49:41 +0000	[thread overview]
Message-ID: <bug-11731-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11731

            Bug ID: 11731
           Summary: buildroot 2019.02 systemd - long start Network name
                    resolution service
           Product: buildroot
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: skif at skif-web.ru
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 7971
  --> https://bugs.busybox.net/attachment.cgi?id=7971&action=edit
screenshot with error

Hello!
After upgrade to buildroot 2019.02 I have a problem with Network name
resolution.

On startup, system write: A start job in running for Network name resolution.

After 3 minutes: [FAILED] failed to start Network Name resolution, and it all
starts again.

But, if i press any key, system boot go on and /etc/resolv.conf in correct.

What i do wrong ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-03-21  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  9:49 bugzilla at busybox.net [this message]
2019-03-31 19:37 ` [Buildroot] [Bug 11731] buildroot 2019.02 systemd - long start Network name resolution service bugzilla at busybox.net
2019-04-01 14:58 ` bugzilla at busybox.net
2024-06-15 14:49 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11731-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.