Upstart 1.3 is in Ubuntu oneiric.
** Changed in: upstart (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720573
Title:
Segmentation fault on
Note that the fix for this bug in Upstart 1.3 protects against .conf
and .override.
** Changed in: upstart (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: upstart
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720573
Title:
Segmentation fault on .conf file in /etc/init
--
ubuntu-bugs mailing
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720573
Title:
Segmentation fault on .conf file in /etc/init
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Confirmed this just now on the latest upstart in natty
** Changed in: upstart
Status: New = Confirmed
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
** Changed in: upstart (Ubuntu)
Confirmed; interestingly this doesn't seem to cause a kernel panic if
the file already exists on startup, just on first creation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720573
Title:
The attached patch adds test cases to check for this case, along with a
simpler similar test case for a file missing the .conf extension
(which is tested elsewhere, but always worth checking again).
This shows that the failure is an assertion:
test:job_class.c:153: Assertion failed in
The reason it doesn't cause a panic on the reboot is because the file
doesn't actually get to the filesystem! If it did, you wouldn't be able
to boot again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The best fix is in the filter, since it covers both.
As well as just checking that there is a .conf extension, make sure
that the previous character isn't /
** Changed in: upstart
Status: Triaged = In Progress
** Patch added: conf-file-fix.patch
http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1260
** Changed in: upstart
Status: In Progress = Fix Committed
** Changed in: upstart
Milestone: None = 1.0
** Changed in: upstart
Assignee: (unassigned) = Scott James Remnant (scott)
--
You received this bug
It must be a race between the metadata comitting to the fs and the
segfault because the vm I tested this on is un-bootable without
init=/bin/bash now.
On Feb 17, 2011, at 3:07 PM, Scott James Remnant
720...@bugs.launchpad.net wrote:
The reason it doesn't cause a panic on the reboot is because
11 matches
Mail list logo
