Skip to contentSkip to conversation

New: Systemd spawns two getty processes when the getty port is set to console

Buildroot bugzilla at busybox.net 1 participant 6 messages Apr 18, 2020 – May 19, 2020

lore
Share & tools
lore
#0 lore 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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

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

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

--- Comment #1 from Matt Weber <[email protected]> ---
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 :-)

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#2 lore raw

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

In reply to bugzilla at busybox.net

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

--- Comment #2 from Adam Duskett <[email protected]> --- 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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#3 lore raw

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

In reply to bugzilla at busybox.net

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

Adam Duskett <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

   Target Milestone|---                         |2020.05
                 CC|                            |aduskett at gmail.com
Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#4 lore raw

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

In reply to bugzilla at busybox.net

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

--- Comment #3 from Thomas Petazzoni <[email protected]> --- 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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#5 lore raw

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

In reply to bugzilla at busybox.net

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

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #4 from Thomas Petazzoni <[email protected]> ---

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

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.