https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c1 --- Comment #1 from Stephan Kulow 2011-10-22 21:05:03 CEST --- You're free to use sysvinit for 12.1 and it will continue to delay getty till everything is started. but I don't see this as an improvement. systemd is just different. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c3 --- Comment #3 from Frederic Crozat 2011-10-24 08:24:44 UTC --- Unfortunately, there is no easy way to delay startup of getty1 until everything is "started". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c5 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #5 from Frederic Crozat 2012-06-21 10:53:25 UTC --- reopening, upstream systemd has now a concept of "idle" service, which is used for agetty so they are only started once other services are running. However, it is only available with systemd >= 184 and I don't plan to push it for 12.2. Keeping this bug opened until we have systemd >= 184 in Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c7 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|booting with systemd leads |systemd-init boot puts |to strange boot output |messages on tty1 after | |agetty starts --- Comment #7 from Felix Miata 2012-06-21 13:15:44 UTC --- Changing subject to make discoverable via Bugzilla search. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c9 --- Comment #9 from Felix Miata 2013-02-01 10:33:36 UTC --- This is happening with (default) systemd-init boot too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c11 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | --- Comment #11 from Felix Miata 2013-02-01 14:00:28 UTC --- I didn't see that the assignee got changed by Bugzilla, so I've reverted that. History isn't showing a QA change. I don't see any way to change the "found in". I changed the product (that it can be fixed in). I only change "priority" if I'm assigned the bug. Whether "importance" which is currently "major" should be something else isn't clear to me. Since it doesn't prevent use, I wouldn't call it a blocker or even critical. Since you filed it, maybe you want to change "severity". The problem for me is I set tty1 to noclear, so messages following the login prompt obfuscate its existence so that I often can't even tell init is finished except by tapping <ENTER> to force a prompt redraw. Plus, if I switch to another tty as soon as it's possible, which is what I do on most boots so as to leave init messages on tty1 for the duration of uptime, the extra messages litter it instead. To me it's cosmetically repulsive, not a true blocker. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c13 --- Comment #13 from Felix Miata 2013-03-01 20:19:03 UTC --- Using 12.3RC2 on a P4 family 15 model 2 stepping 9 2.6GHz booting with 3 on cmdline puts 13 rows of messages (re: network, scheduler, LSB*) on tty1 following login prompt. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c15 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #15 from Frederic Crozat 2013-03-11 15:32:19 UTC --- please attach output of "systemd-analyse plot > boot.svg" on one affected system. But I doubt we will be able to do more than what is done upstream now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c17 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|mrmazda@earthlink.net | --- Comment #17 from Felix Miata 2013-03-12 13:11:29 UTC --- oops -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c18 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #18 from Frederic Crozat 2013-03-12 14:08:49 UTC --- if you are relying on network login, a dependency is missing (tracked on bnc#803471 ) if you aren't, because you don't have plymouth installed, there is no other dependency to start getty@tty1.service other than waiting for 5s max after all services needed for basic.target are started. Plymouth is adding another dependency (waiting for rc-local.service to be done, which is waiting for network.target) but there is no pro to enforce this when plymouth is not installed. We can't improve this behaviour anymore. Sorry. Closing as FIXED. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c20 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #20 from Frederic Crozat 2013-03-13 09:23:17 UTC --- (In reply to comment #19)

Bug 803471 is NA here.

Can't some artificial depends be placed in rc-local.service or elsewhere to ensure long enough wait before getty@tty1.service starts, maybe agetty itself, or getty, or numlock?

No, because it is artifical.

As a sort of workaround, what about a user configurable fixed length wait for tty1, but allowing tty[2-6] availability as soon as everything agetty requires has finished? I rarely log in on tty1 anyway, reserving it for the boot messages until such time as may come that I need more than 5 ttys doing something at once?

No, there won't be a configuration for this. Sorry again, but I'm closing it. Feel free to open a bug upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c22 --- Comment #22 from Frederic Crozat 2013-03-13 09:57:18 UTC --- I don't plan to work on this anymore. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c24 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos.e.r@opensuse.org --- Comment #24 from Carlos Robinson 2013-06-15 04:04:03 UTC --- I have this local job: /etc/systemd/system/helloworld.service [Unit] Name=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target [Service] Type=oneshot RemainAfterExit=true ExecStart=-/usr/local/bin/helloworld [Install] WantedBy=multi-user.target helloworld is a script that plays a sound. Till I hear that sound, I wait, booting has not finished and it is pointless to login. If you place a similar condition on the getty service, it will wait. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c25 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |werner@suse.com Resolution| |FIXED --- Comment #25 from Dr. Werner Fink 2013-12-04 20:20:43 UTC --- IMHO this bug is fixed. I'm booting a 12.3 as well as a 13.1 and both do show a normal agetty on tty1 *after* the boot is complete ... or should I say that the messaghes are not on tty1 but on an other tty ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.