Comment 8 for bug 652221

On Mon, Oct 04, 2010 at 03:39:14AM -0000, Michael Hudson-Doyle wrote:
> It seems to be present, but possibly not starting for some reason? I
> don't speak upstart well enough to understand the following:

> root@localhost:~# status openvt
> openvt start/pre-start, process 495

If this is reproducible, next time you hit this can you please see what the
PID listed as 'openvt start/pre-start' is doing? This suggests that we've
hung trying to run 'exec stop tty1', which should be a trivial operation.
Getting the 'ps' output, strace output, and a backtrace would help.

On Mon, Oct 04, 2010 at 04:13:32AM -0000, Michael Hudson-Doyle wrote:
> Hmm, again with the utter lack of upstart chops, I think this might be
> some kind of race between the openvt and tty1 jobs. Maybe the openvt
> job is being started and so 'stop tty1' is being called before the tty1
> job fully starts up, or something.

The intended behavior here is:

 - the start conditions for the tty1 job are met.
 - upstart sees that openvt is 'start on starting tty1' and processes it
   first.
 - the pre-start script runs and sets the tty1 job back to 'stopped' state
   with no further processing
 - the openvt exec line runs, and the openvt job is marked as
   'start/running'

Starting the openvt job manually does the same thing, except that 'exec stop
tty1' is a no-op if tty1 is already stopped.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>