From: Thomas Steudten <alpha@steudten.com>
To: Calin Cosma <calin_cosma@mymail.ro>
Cc: linux-admin@vger.kernel.org
Subject: Re: RPM issue on 2.6.5
Date: Tue, 27 Apr 2004 14:36:52 +0200 [thread overview]
Message-ID: <408E53E4.8020808@steudten.com> (raw)
In-Reply-To: <1083068904.1925.26.camel@ProfiLinux.bucharest-mof.ro.ibm.ro>
Reason?
It seems to be problem with the O_SYNC flag in the open() call from libc
and of rpm and of db4, don't know exact. Google the web for more information.
O_SYNC The file is opened for synchronous I/O. Any writes on the
resulting file descriptor will block the calling process until
the data has been physically written to the underlying hardware.
The LD_ASSUME_KERNEL is queried in the libc, so it should be better
to set it only if you run rpm.
Version varies from 2.2.5 to 2.4.1. If you look in the glic sources, you will
see more.
Calin Cosma wrote:
> On Tue, 2004-04-27 at 13:59, Thomas Steudten wrote:
>
>>Update your rpm version to RH 4.2-2, your db4 to 4.0.14-20
>>OR set the environment variable as a workaround to
>>export LD_ASSUME_KERNEL=2.2.5
>>
> It worked with the environment setting. Still I don't want to ask dumb
> question, but could explain me which is the reason for this?
--
Tom
LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?
prev parent reply other threads:[~2004-04-27 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 9:13 RPM issue on 2.6.5 Calin Cosma
2004-04-27 10:59 ` Thomas Steudten
2004-04-27 12:31 ` Calin Cosma
2004-04-27 12:36 ` Thomas Steudten [this message]
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=408E53E4.8020808@steudten.com \
--to=alpha@steudten.com \
--cc=calin_cosma@mymail.ro \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).