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?
- : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
