SRU team: I think we should waive the need to pass verification on this
bug, and allow it to enter maverick/lucid updates. It is a very small
patch, and no doubt does good. It has been in the respective proposed
pockets for a long time, so regressions don't seem likely.
Thoughts?
--
You
in my Bug #789419, which has been marked a duplicate, i was told to
enable lucid-proposed but i don't even have sysvinit installed so i fail
to see how it has been fixed and why it is a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On Wed, Oct 19, 2011 at 01:14:35AM -, scar wrote:
in my Bug #789419, which has been marked a duplicate, i was told to
enable lucid-proposed but i don't even have sysvinit installed so i fail
to see how it has been fixed and why it is a duplicate.
You would need to install the initscripts
initscripts is already the latest version 2.87dsf-4ubuntu17.4 from
lucid-updates, there is no update in lucid-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665185
Title:
Indeed, the latest version of sysvinit in lucid-updates includes this
change; apparently the version fixing this bug was later superseded by
another fix that didn't mention this change in its changelog. Marking
as fixed for lucid.
I think that's evidence that bug #789419 is not a duplicate of
This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu19.2
---
sysvinit (2.87dsf-4ubuntu19.2) maverick-proposed; urgency=low
[ Dan Muresan ]
* sendsigs: OMITPIDS needs to be reinitalized for every loop iteration
before concatanating pids of upstart jobs to it. Otherwise
There is no proper TEST CASE for this bug, which may explain why it has
not been verified.
Dan/Surbhi, can you please add a full TEST CASE as required in
https://wiki.ubuntu.com/StableReleaseUpdates ? This bug has sat on the
-proposed heap far too long without verification.
--
You received
** Branch linked: lp:ubuntu/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665185
Title:
/etc/init.d/sendsigs fails to kill some processes
To manage notifications about this bug go to:
** Branch linked: lp:ubuntu/lucid-proposed/sysvinit
** Branch linked: lp:ubuntu/maverick-proposed/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665185
Title:
/etc/init.d/sendsigs fails to
Is there any progress on verification of lucid, it's blocking other
fixes. Thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665185
Title:
/etc/init.d/sendsigs fails to kill some processes
Martin Pitt Unfortunately, this doesn't work for me. The problem
remains, computer doesn't shut down at all. Acer Extensa 3000, Lucid
Lynx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665185
Title:
There are other bugs in Ubuntu that can cause shutdown problems, for
example Bug #665195 and bug #665176.
I fixed my problems by creating a /etc/init.d/sysshutdown as attached
(and adding it to the various runlevels). This at least gives you a
chance to examine the situation (in Virtual Console
Thanks for your reply, Dan! I managed to create the sysshutdown file but I
don't know how to do the various runlevels? I did sudo update-rc.d syshutdown
defaults Is it ok this way? Cause if I did it right, then it didn't solve the
problem. I still have to do hard shutdown.
Please note me being
Then please ignore my previous comment and file a separate bug. This bug
is about unclean shutdowns, while yours sounds like the machine hangs on
shutdown -- a different symptom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Accepted sysvinit into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: sysvinit (Ubuntu Lucid)
Michael, agreed. the patch looks good, and should enter lucid-proposed
as soon as the previous SRU for sysvinit passes verification. Since
neither of you were involved with that SRU, you can speed up that
process by verifying that the one preceding your upload works, and
posting your results in
** Attachment added: lucid-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1981801/+files/lucid-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: maverick-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1981802/+files/maverick-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I sponsored them now but they will probably have to wait in the queue
for a little bit longer until the other SRU for sysvinit is verified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665185
Title:
Surbhi, could you propose stable release updates for lucid and maverick
for this? Thanks.
** Also affects: sysvinit (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: sysvinit
** Attachment added: maverick-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1977640/+files/maverick-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lucid-proposed-debdiff
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1977641/+files/lucid-proposed-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I sponsored the lucid and maverick uploads now, many thanks Surbhi for
the porting.
** Changed in: sysvinit (Ubuntu Lucid)
Status: Triaged = In Progress
** Changed in: sysvinit (Ubuntu Maverick)
Status: Triaged = In Progress
--
You received this bug notification because you are a
Great, thanks. Now what do I have to do to get this fix into Lucid,
where it actually *is* a problem (killall5 doesn't overflow on Natty,
because it's been fixed, but it does on Lucid)?
The LTS release still has years left of support, but I'm really getting
the all-around feeling that it is
** Attachment added: debdiff of initscripts between 1) existing natty source
and 2) patch given by the bug reporter applied
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1949315/+files/debdiff_665185
--
You received this bug notification because you are a member
This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu22
---
sysvinit (2.87dsf-4ubuntu22) natty; urgency=low
[ Dan Muresan ]
* sendsigs: OMITPIDS needs to be reinitalized for every loop iteration
before concatanating pids of upstart jobs to it. Otherwise it overflows
Dan,
I think my thought process here was that any PID belonging to an upstart
job at the time this was run is astronomically unlikely to get reused
for a different process during the shutdown sequence, and I don't think
I noticed that we're requerying the list of pids repeatedly in a loop
and
Steve, note that while this issue has been masked in Maverick Natty by
making killall5 accept any number of OMITPIDs, it is still a problem in
Lucid for those who have upstart jobs that won't shut down. The symptom
is a journal replay (or heaven forbid worse) after every single reboot
(because
** 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/665185
Title:
/etc/init.d/sendsigs fails to kill some processes
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug has not been fixed in Lucid and is still present in Natty
(mitigated there by a fixed killall5 (which has no hard limit on the
omitpid buffer). Ubuntu Lucid should either patch
/etc/init.d/sendscripts as per in my original report (and attached
patch), or backport killall5. This is a
--
/etc/init.d/sendsigs fails to kill some processes
https://bugs.launchpad.net/bugs/665185
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I wonder why ubuntu-bug filed this report against sysvinit? The problem
is in the initscripts package, and that's what I originally requested...
--
/etc/init.d/sendsigs fails to kill some processes
https://bugs.launchpad.net/bugs/665185
You received this bug notification because you are a member
32 matches
Mail list logo
