Bug 3076 - updatedb fails... cannnot open db locate fails too...
updatedb fails... cannnot open db locate fails too...
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-26 17:31 EDT by okosamastarr
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-08 21:14:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description okosamastarr 1999-05-26 17:31:52 EDT
On a fresh vanilla RHL 6.0 english installation with all
updates applied updatedb and locate fails. the
decrypt_database open function fails.
(maybe a MD5 PW problem ???).

on a GERMAN installation many translations (e.g. mc) crashes
the input masks (even during install).

upgrade of previous (Apollo kernel 2.0.xx) Versions goes
*very* poor. It's the best way to backup /home data and
reinstall.

english install with german latin1 keymap works fine, but
after setting LANG=de etc. in .bash_profile various programs
will *not* run (such as man, less...).

That's a Problem with the glibc 2.XX and the "new" native
language support...
Comment 1 Jeff Johnson 1999-05-26 19:22:59 EDT
The functionality of updatedb/locate has been replaced with
a package called slocate.
Comment 2 Jeff Johnson 1999-06-05 12:04:59 EDT
The slocate problem is solved by upgrading to slocate-1.6 and running
updatedb manually.

I've changed the component to glibc in order to resolve the NLS
issues.
Comment 3 Jay Turner 1999-06-28 11:59:59 EDT
This issue has been assigned to a developer for further action.
Comment 4 Cristian Gafton 1999-07-08 21:14:59 EDT
This is not a glibc problem, and besides, "LANG=de man bash" works for
me.

There must be something weird going on with that installation.

Note You need to log in before you can comment on or make changes to this bug.