** Changed in: eglibc (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cann
I've no idea why that revision got dropped from the Ubuntu package, I
did a bit of investigation and it seems to vanish about the point we
switched to the auto-importer based packages. My only guess is that
bzr undid the cherry-pick as part of a merge.
Right, eglibc's postinst should definitely n
Some day, I'll learn to pay attention to the details, I promise. Sorry
for the confusion.
Ok, so I reverse merged r977 back in, which mostly applied cleanly.
I then tested this on a natty VM, and, shock, it worked flawlessly.
I think we may also need to have eglibc's postinst skip the call to
te
** Branch linked: lp:~clint-fewbar/ubuntu/natty/upstart/restore-re-exec-
code
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown becaus
Yes, I know how to drive bzr and dpkg ;-)
My point is that if you do that diff, the only occurrence of SIGTERM
is in the code for the upstart/udev bridge, that patch doesn't add any
handling to upstart itself.
Scott
On Wed, Dec 29, 2010 at 6:54 AM, Clint Byrum wrote:
> On Wed, 2010-12-29 at 00:
On Wed, 2010-12-29 at 00:06 +, Scott James Remnant wrote:
> Are you sure? I can't find that code at all - it looks like it's been
> lost somehow
quite certain.. its a bit tricky to find it in bzr, but this will give
it to you for, say, maverick:
$ bzr branch lp:ubuntu/maverick/upstart maveri
Are you sure? I can't find that code at all - it looks like it's been
lost somehow
On Tue, Dec 28, 2010 at 6:19 PM, Clint Byrum wrote:
> On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
>> On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum wrote:
>>
>> > This makes sense, because telinit
On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
> On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum wrote:
>
> > This makes sense, because telinit u just sends SIGTERM to upstart, which
> > has no handler, as it was removed by revision 977, and doesn't seem to
> > have been added back. S
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum wrote:
> This makes sense, because telinit u just sends SIGTERM to upstart, which
> has no handler, as it was removed by revision 977, and doesn't seem to
> have been added back. Since SIG_DFL signals are not delivered to init,
> I'm not sure how umoun
Oops, I'm still learning my way around the shutdown process and, indeed,
I missed umountroot.
I went ahead and added another lsof right after the call to telinit u,
right before MOUNT_FORCE_OPT=, and one *after* the remount of /.
It doesn't seem to make any difference:
cl...@natty-alpha1:~$ grep
101 - 110 of 110 matches
Mail list logo
