From: Ben Greear <greearb@candelatech.com>
To: Dave Jones <davej@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: futex hang with rpm in 2.6.17.1-2174_FC5
Date: Sat, 21 Oct 2006 11:08:44 -0700 [thread overview]
Message-ID: <453A622C.2020401@candelatech.com> (raw)
In-Reply-To: <20061021180005.GF30758@redhat.com>
Dave Jones wrote:
> On Sat, Oct 21, 2006 at 10:45:02AM -0700, Ben Greear wrote:
> > Dave Jones wrote:
> > > On Fri, Oct 20, 2006 at 11:38:58AM -0700, Ben Greear wrote:
> > > > I had a dead nfs server that was causing some programs to pause,
> > > > in particular 'yum install foo' was paused. I kill -9'd the
> > > > yum related processes.
> > > >
> > > The dead rpm you killed left behind locks in its databases.
> > > rm -f /var/lib/rpm/__db* and it should work again.
> > >
> > I'll give that a try, but shouldn't these locks clean themselves up when the
> > process is killed
>
> If you kill -9'd the processes, what do you expect to do
> the clean up work ?
>
Well, you can do tricks with file handles so that they are automatically
closed/deleted when
a process exits, even with kill -9. Since this lock is evidently
something in the kernel (since the kernel
call is blocking), then it seems like a similar trick could be crafted.
> > or shouldn't rpm notice the previous process is dead and
> > clean it up itself?
>
> Sounds sensible to me and you, but in the past sensible ideas and
> rpm maintainers haven't gone hand in hand.
>
Ahhh :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2006-10-21 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:38 futex hang with rpm in 2.6.17.1-2174_FC5 Ben Greear
2006-10-21 5:24 ` Dave Jones
2006-10-21 17:45 ` Ben Greear
2006-10-21 18:00 ` Dave Jones
2006-10-21 18:08 ` Ben Greear [this message]
2006-10-21 21:55 ` Ulrich Drepper
2006-11-27 0:02 ` Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453A622C.2020401@candelatech.com \
--to=greearb@candelatech.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox