Re: updatedb not working

2000-01-28 Thread Kevin Dalley
Just download findutils-4.1-37.  The stable version of findutils works
fine.


-- 
Kevin Dalley
[EMAIL PROTECTED]


Re: updatedb not working / bug in updatedb

2000-01-28 Thread Dänzer


--- [EMAIL PROTECTED] 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:
> 
> : [EMAIL PROTECTED]@}

Looks like a relict from autoconf/automake.


> Guess I should file a bug report if I can remember how to do that.

reportbug findutils

Requires that you have a working mail setup, though.


Michel


=
"Software is like sex; it's better when it's free"
 -- Linus Torvalds

"If you continue running Windows, your system may become unstable."
 -- Windows 95 BSOD
__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


Re: updatedb not working / bug in updatedb

2000-01-28 Thread Todd Suess
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, [EMAIL PROTECTED] 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:
> 
> : [EMAIL PROTECTED]@}
> 
> 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] < /dev/null


Re: updatedb not working / bug in updatedb

2000-01-27 Thread debuser
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:

: [EMAIL PROTECTED]@}

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 [EMAIL PROTECTED] 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
> 
> 


updatedb not working

2000-01-27 Thread debuser
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