Launchpad has imported 8 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=431107.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-01-31T20:12:37+00:00 Bill wrote: If you attempt to shutdown/reboot/halt, the halt script just ends up looping endlessly. initscripts-8.62-1 Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/0 ------------------------------------------------------------------------ On 2008-02-11T21:29:25+00:00 Casey wrote: Have we decided if patching killall5 will work for this? Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/1 ------------------------------------------------------------------------ On 2008-02-14T21:44:03+00:00 Bill wrote: It doesn't loop any more, but it doesn't do the right thing either. Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/2 ------------------------------------------------------------------------ On 2008-02-15T23:02:20+00:00 Bill wrote: This is an upstart bug, at least as far as SysV compatibility goes. halt/reboot under SysV check the runlevel when they run - if it's 0 or 6 (reboot/halt), then 'force' is implied. upstart's versions don't have that code, so they just call shutdown again, which starts the loop/hangs. Patch attached momentarily. Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/3 ------------------------------------------------------------------------ On 2008-02-15T23:03:27+00:00 Bill wrote: Created attachment 295051 check runlevel in halt/reboot, set --force accordingly Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/4 ------------------------------------------------------------------------ On 2008-02-16T03:47:16+00:00 Casey wrote: Do we want to apply just this patch to upstart, or both this patch and the no-kill-init sysv patch? I'll roll this in to the rpm tonight. Scott, care to weigh in? Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/5 ------------------------------------------------------------------------ On 2008-02-16T11:19:36+00:00 Scott wrote: That patch is definitely the right solution ;) It didn't affect us because our sysv scripts called halt/reboot with --force anyway Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/6 ------------------------------------------------------------------------ On 2008-02-17T00:22:10+00:00 Casey wrote: Well played then :) Rebuilt upstart package is in koji. We still end up re-executing init on shutdown, but this no longer creates this issue. I may open another bug about that but for now its no big deal. Reply at: https://bugs.launchpad.net/upstart/+bug/388738/comments/7 ** Changed in: upstart (Fedora) Importance: Unknown => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/388738 Title: reboot: should imply --force during shutdown Status in upstart : Fix Released Status in upstart 0.3 series: Won't Fix Status in upstart 0.5 series: Won't Fix Status in upstart trunk series: Won't Fix Status in upstart package in Ubuntu: Fix Released Status in upstart package in Fedora: Fix Released Bug description: https://bugzilla.redhat.com/show_bug.cgi?id=431107 explains. When running halt/reboot while shutting down --force should be implicit. Patch should go to 0.3.11, I tagged for everything else since I'm not sure if this is still present. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/388738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
