Hi!
On Tue, Aug 09, 2005 at 07:33:37AM -0400, Build System wrote:
> glibc-2.3.90-8
> --------------
> * Mon Aug 08 2005 Jakub Jelinek <jakub@xxxxxxxxxx> 2.3.90-8
> - update from CVS
> - nscd persistent database verifier (#164001)
> - cleanup _FORTIFY_SOURCE bits/*.h headers (#165000)
> - handle EINTR in sigwait properly
> - make sure poor man's stack guard randomization keeps first
> byte 0 even on big-endian 32-bit arches
> - fix {elf,nptl}/tst-stackguard1
> - obsolete linuxthreads-devel in glibc-devel
This glibc features a nscd persistent database verifier, which should
especially help with the corrupted nscd persistent databases created
by nscd-2.3.5-10 (original FC4 nscd, which has been miscompiled).
If your /var/db/nscd/* database files were created by nscd-2.3.5-10,
you should likely expect a:
<date> <host> nscd: <pid> invalid persistent database file "/var/db/nscd/passwd": verification failed
<date> <host> nscd: <pid> invalid persistent database file "/var/db/nscd/group": verification failed
<date> <host> nscd: <pid> invalid persistent database file "/var/db/nscd/hosts": verification failed
lines in /var/log/messages after you upgrade and restart nscd.
That just informs you that the old corrupted databases were removed and
recreated from scratch. But afterwards, if you see these messages too
often, something is wrong and you should file a bug report about it.
They might perhaps happen after unclean system shutdown, but certainly
shouldn't be something that appears on every boot.
If the db verifier works well in rawhide, it will be backported.
Jakub
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list