Something reloaded SSH? :)
This will always pop up over your active console until we completely
redo the way we do such messages.
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a mem
The login prompt being held until last on tty1 has been very nice,
Scott, thanks.
However, I have occasionally seen the following, where a seemingly
delayed SSH message pops up:
myhostname login: * Reloading OpenBSD Secure Shell server's configuration sshd
Ideas?
:-Dustin
--
startup messages
This bug was fixed in the package upstart - 0.3.9-2
---
upstart (0.3.9-2) hardy; urgency=low
* Start the getty on tty1 after the rc script has stopped rather then
at the same time it starts to avoid overwriting by console messages.
tty2..6 will still be active if you want an
Sounds reasonable
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
Scott, do you have any comments on the proposed fix for this bug? It
seems to me like a straightforward solution to defer starting the getty
on tty1 until after the rest of rc2 has finished. Perhaps the proposed
patch isn't future-proof against other services being migrated to use
upstart events
Hi, just wanted to still confirm this for the daily build of Hardy, pr
15. march 2008. The attached patch fix the problem
Petter
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a memb
Like Dustin said, you can always switch to tty2 to fix stuff to make bad days
more bearable...
And tty1 can be "pretty" for thoses of us who package appliances.
Best of both worlds?
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You
As a server owner, I want a login as soon as the system is capable of
handling my requests. In fact, I would like a BIOS that would give me
"busybox" like access on a crashed machine.
Think of the bad days and what it takes to make them less bad.
Jim
On 2/20/08, Dustin Kirkland <[EMAIL PROTECTED
On Tue, Feb 19, 2008 at 9:46 PM, peppergrower <[EMAIL PROTECTED]> wrote:
> If you want a login available earlier, then there has to be a
> better way to do it.
You can swap over to tty2+ and get a login there.
Perhaps it should avoid printing the login prompt on *tty1* until all
init scripts ha
See the attachment for why the implementation, at least, is a bug.
Look at the top of that screen dump. When you look at the actual screen
after bootup, the login up top is just barely still on the screen. It
shows up and the system doesn't even pause--it keeps plowing on through
the other scrip
Is this not a feature and not a bug?
http://upstart.ubuntu.com/
System-V init was sequential and if one of the scripts got stuck, you
never got to a login.
There are some race conditions such as ntp and networking.
At least you have a chance of fixing a problem instead of rebooting
into single
@ faulkes:
Same here as well. I installed 7.10 server edition, and selected the
LAMP and Samba options, but never installed a GUI. Still, I had this
bug from the first boot.
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You receiv
Actually,
I just got through installing 7.04 server ppc version, I can confirm that
this behaviour exists
within the ppc version.
However, I did not install X or any components thereof.
Michael
On Feb 19, 2008 1:26 PM, Nick Barcet <[EMAIL PROTECTED]> wrote:
> ** Changed in: upstart (Ubuntu)
>
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => Ubuntu Server Team (ubuntu-server)
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Whew, after some very puzzling results I finally figured out what the
problem was.
When I ran the patch, I included the -b option to create a backup of the
original file; I had never used patch before, so I wanted to make sure I
could get the original back in case I messed things up somehow. This
Could you please attach the output of "cat /etc/event.d/tty1"?
There should be no reason why it wouldn't work after applying my patch :(
Did you try making the changes by hand instead of using my patch?
- Trib'
--
startup messages continue on screen after first login prompt appears
https://bugs
@ Trib' and others:
I'm running Ubuntu server edition 7.10. I was having this problem and
found this site. I downloaded and applied the patch (and checked tty1
to make sure it was applied correctly), and it's not working for me.
Instead, it's now impossible to login using a keyboard. (Fortunate
Raising the priority so that we put some attention to it.
** Changed in: upstart (Ubuntu)
Importance: Low => Medium
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a member of Ubun
Here is a patch file that takes care of the change.
- Trib'
** Attachment added: "Changes the start of tty1 to make sure it starts only
after the last daemon started"
http://launchpadlibrarian.net/11372046/tty1.patch
--
startup messages continue on screen after first login prompt appears
ht
I think the most appropriate solution is to delay tt1 only.
This way the boot messages will be displayed in a proper fashion:
- Boot messages
- (All daemons started)
- Show the login prompt
Login via ssh is not affected in any way, and most probably this is how system
admins will login to a headl
Suggest consideration of the order you actually want the events to happen.
Is it a good idea to allow users to login before the standard daemons have been
started?
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug
This seems to affect the (still alpha) version of Hardy.
The "fix" you propose still works though.
** Tags added: feisty hardy server startup upstart
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification b
I like your solution Dario (I have not tested it yet). However, I'm not
sure it should be considered a fix. Before applying this workaround,
tty1 was being started earlier. We were forced to delay tty1, and
therefore the appearance of the login prompt, due to rc2's output
messages. But if the logge
Joshua, sadly your solution does not work for me: I mean, getty is not
started at the BEGINNING of runlevel 2, but neither at the end, even
with "exec start tty1" in /etc/init.d/rc (I really don't know why).
However, I found a better solution: since upstart is event-based, you
simply need to tell i
Thanks, Joshua! Your workaround worked flawlessly here.
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
Thanks Jakson... incidentally my workaround of adding "-q" after rc does
NOT work. Some or all of the scripts in /etc/rc2.d did not get executed
when I did that. Then Gnome started complaining that it failed to
initialize HAL and such.
Here's a workaround that's a bit more upstartish, I think.
*
My not elegant solution was the creation of a script named /etc/init.d
/restart-tty1 with the following content:
#!/bin/sh
stop tty1
clear
start tty1 > /dev/null
And, then, a symbolic link to it at /etc/rc2.d named S99zrestart-tty1. I
have chosen the prefix S99z to be sure that it will be the la
Does anyone have a workaround for this? Other than inserting -q into
rc2: "exec /etc/init.d/rc -q 2"
Ideally one that allows the info to be captured to a log. I've tried
"console none" and "console logged" in rc2 but they didn't seem to have
any effect.
--
startup messages continue on screen aft
Still present in Ubuntu Server 7.10 - no GUI installed here.
It is *quite* annoying, not worth throwing the toys out of the pram for
though.
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because yo
Perhaps not just annoying, but confusing as well.
We have received feedback from users who were confused there was no
login prompt. Pressing will display a prompt, but it is
seemingly non-intuitive to new users.
And then there is the argument that other dists don't have this
"problem".
--
sta
a guy named steve made the following comment about our server distro on
slashdot :
"A boot screen that doesn't look like vomited output. Why does the
login prompt appear before services have finished loading? I support
being able to use the machine before services have stopped. I do not
need "Star
Occurs because the getty is started at the beginning of rc2 rather than
the end; easy fix would be to start the getty at the end of the runlevel
(after the script is finished) or to fix the messaging in the first
place
--
startup messages continue on screen after first login prompt appears
https:
Boot messages dicussion scheduled (again) for UDS
** Changed in: upstart (Ubuntu)
Status: Confirmed => Triaged
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a member of Ubunt
I confirm this bug on a custom Feisty desktop installation from
alternate CD.
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
Assigning to upstart.
** Changed in: upstart (Ubuntu)
Sourcepackagename: None => upstart
Status: New => Confirmed
** Changed in: upstart (Ubuntu)
Importance: Undecided => Low
--
startup messages continue on screen after first login prompt appears
https://bugs.launchpad.net/bugs/65230
As you can see from line "a" above, the login prompt actually is
displayed, however it is displayed before the initscripts are run. If
you press enter, the login prompt should reappear.
I am experiencing the same problems with Feisty (Server edition).
I tried changing the setting "DELAYLOGIN" in
36 matches
Mail list logo
