[Buildroot] [Bug 12786] New: Systemd spawns two getty processes when the getty port is set to console

[Buildroot] [Bug 12786] New: Systemd spawns two getty processes when the getty port is set to console

[bugzilla at busybox.net]

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.

[Buildroot] [Bug 12786] Systemd spawns two getty processes when the getty port is set to console

[bugzilla at busybox.net]

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

--- Comment #1 from Matt Weber <matthew.weber@rockwellcollins.com> ---
 I can confirm I see similar with aarch64 build using master.  I noticed it is
possible to login and run commands you just have to keep escaping the new getty
:-)

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

[Buildroot] [Bug 12786] Systemd spawns two getty processes when the getty port is set to console

[bugzilla at busybox.net]

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

--- Comment #2 from Adam Duskett <aduskett@gmail.com> ---
After I did a quick google search I found a post on stack exchange that
indicates this has been an issue since at least version 2019.02!

https://unix.stackexchange.com/questions/566959/how-to-prevent-console-getty-service-to-start

The logic behind /dev/console in systemd.mk is a bit complex and I am not sure
where to start.

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

[Buildroot] [Bug 12786] Systemd spawns two getty processes when the getty port is set to console

[bugzilla at busybox.net]

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

Adam Duskett <aduskett@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |2020.05
                 CC|                            |aduskett at gmail.com

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

[Buildroot] [Bug 12786] Systemd spawns two getty processes when the getty port is set to console

[bugzilla at busybox.net]

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

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I have J?r?my Rosen to have a look, see
http://lists.busybox.net/pipermail/buildroot/2020-May/282962.html. I must say
the logic in systemd.mk is very confusing, and the comment above it doesn't
help understand what's going on.

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

[Buildroot] [Bug 12786] Systemd spawns two getty processes when the getty port is set to console

[bugzilla at busybox.net]

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

Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---


*** This bug has been marked as a duplicate of bug 12361 ***

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