@Adam: the point here is that Upstart is signalling an error, albeit a
soft one. However, in all cases it will be a transitory error since at
some point in the boot /dev/pts _will_ be mounted.
For i386/amd64 Ubuntu images, Ubuntu currently uses an initramfs which
is responsible for setting up /dev/pts. In the case of ARM where you
have no initramfs, /dev/pts will not be mounted when Upstart starts.
Currently the problem will 'correct itself' once mountall has finished
since it will mount /dev/pts if not already mounted. So, currently if
you have no initramfs you will get one message / job that Upstart
started before /dev/pts is available.
The full solution to this problem involves a bit of redesign since the
mountall model doesn't work well if you have no initramfs -- unless you
disable job logging. A pragmatic fix would be to have Upstart mount /dev
and /dev/pts itself and if that fails continue to display the message
with the addition of the job name so it is clear which jobs will not
have their output logged.
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980917
Title:
Failed to create pty - disabling logging for job
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
