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 12786] New: Systemd spawns two getty processes when the getty port is set to console
Date: Sat, 18 Apr 2020 01:17:44 +0000	[thread overview]
Message-ID: <bug-12786-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12786
           Summary: Systemd spawns two getty processes when the getty port
                    is set to console
           Product: buildroot
           Version: 2020.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: aduskett at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Very straight forward.

When systemd is selected as the init system, and BR2_TARGET_GENERIC_GETTY_PORT
is set to console, two gettys are spawned which prevents a user from logging
in.

How to reproduce:

make qemu_x86_64_defconfig
menuconfig -> System configuration -> Init system -> systemd
make

Then run the resulting image.

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

             reply	other threads:[~2020-04-18  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18  1:17 bugzilla at busybox.net [this message]
2020-04-18 21:40 ` [Buildroot] [Bug 12786] Systemd spawns two getty processes when the getty port is set to console bugzilla at busybox.net
2020-04-19 18:53 ` bugzilla at busybox.net
2020-04-19 18:54 ` bugzilla at busybox.net
2020-05-16 14:29 ` bugzilla at busybox.net
2020-05-19 21:39 ` bugzilla at busybox.net

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-12786-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.