Re: updatedb not working / bug in updatedb
I noticed this as well, and I fixed it by copying frcode into the same dir
as the updatedb program, it then works fine. I know it's a quick fix, but it
worked.
Regards,
Todd
On Thu, 27 Jan 2000, debuser@platinum.globalmart.com wrote:
> After more tinkering around, I think I've found the problem. The problem
> is that updatedb is not able to execute the frcode program which it calls
> to compress the database. In looking at an older version of updatedb, it
> contains the line:
>
> : ${LIBEXECDIR=/usr/lib/locate}
>
> but the version from potato has the line:
>
> : ${LIBEXECDIR=@libexecdir@}
>
> I'm not much of a shell hacker so I don't know what @libexecdir@ is
> supposed to do, but evidently it's not setting the path correctly so
> frcode is not being run and updatedb dies without creating the file.
> Guess I should file a bug report if I can remember how to do that.
>
> Gerry
>
> On Wed, 26 Jan 2000 debuser@platinum.globalmart.com wrote:
>
> > I'm using potato. Today I tried doing "locate filename" and I got
> > "warning /var/lib/locate/locatedb more than 8 days old". My understanding
> > is that this is supposed to be updated daily via cron in the script
> > /etc/cron.daily/find. I wondered if cron was broken so I tried running
> > the script manually. The file /var/lib/locate/locatedb was not modified.
> > So, it seems as if updatedb is broken on my system. Or is something else
> > wrong with my system?
> >
> > Thanks,
> >
> > Gerry
> >
> >
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: