From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@digeo.com>
Cc: rpjday@mindspring.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.66-bk12 causes "rpm" errors
Date: 06 Apr 2003 23:35:11 -0400 [thread overview]
Message-ID: <1049686511.894.10.camel@localhost> (raw)
In-Reply-To: <20030406202926.762754ea.akpm@digeo.com>
On Sun, 2003-04-06 at 23:29, Andrew Morton wrote:
> But that's a different error. Robert (Day) reported:
>
> rpmdb: unable to join the environment
> error: db4 error(11) from dbenv->open: Resource temporarily unavailable
> error: cannot open Packages index using db3 - Resource temporarily unavailable (11)
> error: cannot open Packages database in /var/lib/rpm
>
> but then again, there's no way in which the patch which we're discussing
> could cause EAGAIN.
Oh, sorry for not mentioning. I see both... I think it depends whether a
previous error left a stale lock around. Its the same problem, trust
me.
> Has anyone straced a failing rpm command?
I sent one out...
Robert Love
next prev parent reply other threads:[~2003-04-07 3:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 1:18 2.5.66-bk12 causes "rpm" errors Robert P. J. Day
2003-04-07 1:32 ` Andrew Morton
2003-04-07 1:41 ` Robert Love
2003-04-07 1:47 ` Robert Love
2003-04-07 11:45 ` Alan Cox
2003-04-07 14:53 ` Robert Love
2003-04-07 14:17 ` Alan Cox
2003-04-07 1:49 ` Robert Love
2003-04-07 2:59 ` J Sloan
2003-04-07 12:07 ` Robert P. J. Day
2003-04-07 2:04 ` Robert P. J. Day
2003-04-07 1:28 ` Andrew Morton
2003-04-07 3:15 ` Robert Love
2003-04-07 3:19 ` Robert Love
2003-04-07 3:29 ` Andrew Morton
2003-04-07 3:35 ` Robert Love [this message]
2003-04-07 9:05 ` Felipe Alfaro Solana
-- strict thread matches above, loose matches on Subject: below --
2004-04-20 8:10 Fred Shaul
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=1049686511.894.10.camel@localhost \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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