[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

[Paul Crawford]

In the long run, migrating all of the DB files to newer ones that
identify the size/swap nature is the right approach, however, I wonder
if a simpler fix for 'man' which would be useful for current systems
would be to keep everything in the in local DB (say the
/var/cache/man/index.db file or similar) but to allow that to index any
files discovered by its optimistic searching of anywhere along the $PATH
locations?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to man-db in Ubuntu.
https://bugs.launchpad.net/bugs/1001189

Title:
  'man' command fails with lseek error opening cross-architecture
  index.db file (on network share)

Status in “gdbm” package in Ubuntu:
  Confirmed
Status in “man-db” package in Ubuntu:
  Confirmed

Bug description:
  When trying to look up the on-line documentation using the 'man'
  command it fails on 12.04 with lseek error. For example:

  $ man resolvconf
  gdbm fatal: lseek error

  This lseek error applies to other requests as well (e.g. ls, fdisk,
  etc). System information is:

  $ lsb_release -rd
  Description:	Ubuntu 12.04 LTS
  Release:	12.04

  apt-cache policy man
  man:
    Installed: (none)
    Candidate: (none)
    Version table:

  However, it is installed since it runs as a command, and I find:

  $ which man
  /usr/bin/man

  $ man --version
  man 2.6.1

  What I expect is to read the manual page appropriate to the
  command/program, and not get a software error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdbm/+bug/1001189/+subscriptions