Still affects Ubuntu
** Changed in: upstart (Ubuntu)
Status: Invalid => Triaged
--
upstart utterly fails when /bin/sh symlink disappears
https://bugs.launchpad.net/bugs/65024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Changed in: upstart
Status: Fix Committed => Fix Released
--
upstart utterly fails when /bin/sh symlink disappears
https://bugs.launchpad.net/bugs/65024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Trunk now has better handling of failures in the child process whilst
still inside Upstart's own code, specifically it can catch an exec()
failure and obtain the error number.
In practice, there's little we can realisitically do; but we do at least
log the problem ("No such file or directory") and
** Changed in: upstart
Status: Confirmed => Triaged
** Changed in: upstart
Target: None => 0.5
--
upstart utterly fails when /bin/sh symlink disappears
https://bugs.launchpad.net/bugs/65024
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Depends on having feedback of whether exec(), etc. failed; once we have
that, if exec() of /bin/sh fails, we can execute some appropriate
fallback.
I'm going to suggest something like /sbin/sulogin --missing-shell as a
standard "OMG! THE SKY IS FALLING!" escape route. Of course, if your
sulogin i
** Changed in: upstart (upstream)
Target: 0.3 => None
--
upstart utterly fails when /bin/sh symlink disappears
https://bugs.launchpad.net/bugs/65024
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
Rejecting the Ubuntu portion of this bug, since the dependency on a
working /bin/sh is internal to the upstart code and not a by-product of
the Ubuntu rules.
** Changed in: upstart (Ubuntu)
Status: Confirmed => Rejected
--
upstart utterly fails when /bin/sh symlink disappears
https://bugs
** Changed in: upstart (upstream)
Assignee: Scott James Remnant => (unassigned)
** Changed in: upstart (Ubuntu)
Assignee: Scott James Remnant => (unassigned)
--
upstart utterly fails when /bin/sh symlink disappears
https://launchpad.net/bugs/65024
--
ubuntu-bugs mailing list
ubuntu-b
Seems to have been a wrong entry in fstab that caused the problem - is
solved for me.
--
upstart utterly fails when /bin/sh symlink disappears
https://launchpad.net/bugs/65024
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I am being hit hard by this. After playing around with gconf, I cannot
boot anymore. The initial output showed that /bin/sh cannot be executed.
I booted with a Live CD and corrected the symlink for /bin/sh, which
linked to dash. After linking it to bash, I still have the following
output:
/etc/rcS
** Changed in: upstart (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Scott James Remnant
Status: Rejected => Confirmed
--
upstart utterly fails when /bin/sh symlink disappears
https://launchpad.net/bugs/65024
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Changed in: upstart (upstream)
Target: None => 0.3
--
upstart utterly fails when /bin/sh symlink disappears
https://launchpad.net/bugs/65024
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The principal problem here is that /bin/sh is hardcoded as something to
use in job_run_* -- we should check for exec failing and have some kind
of fallback.
Perhaps just exec'ing /sbin/sulogin directly is appropriate?
** Changed in: upstart (Ubuntu)
Status: Unconfirmed => Rejected
** Also
13 matches
Mail list logo
