Gerry wrote:
> On Thu, 7 Oct 2004, jdh13 wrote:
>
>
>>hello all,
>>i used locate from findutils on sol7, sol8 and sol9.
>>findutils came from sunfreeware.com or blastwave.org or from sun cd
>>companion.
>>Sine few months, locate seg fault on sol8, and on sol9, when i launch
>>updatedb, it runs during 2 days and consumes 100% cpu still i kill it
>>i search on google, not finding a solution
>>findutils is 4.1 and seems not released since 1994
>>
>>i try to recompile it, but obtain the same result
>
>
> ./configure --program-prefix=g please : >
>
it depends, on sunfreeware, there isn't "g", on blastwave, yes

>>scr-henry% truss ./locate/locate runtest
>>
>>read(3, " r i m e n t A T - t h e".., 8192) = 8192
>>read(3, " t o . e p s\0\n f i g\0".., 8192) = 8192
>> Incurred fault #6, FLTBOUNDS %pc = 0x000124DC
>> siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3
>> Received signal #11, SIGSEGV [default]
>> siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3
>> *** process killed ***
>>anybody can help?
>
>
> Maybe. You will get seg faults when you dont alter PRUNEPATHS
> to include directories like /proc... eg:
> : ${PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /proc"}
>
great! many thanks it works now!
i did:
updatedb --prunepaths='/tmp /usr/tmp /var/tmp /home /proc /var/run'
i added /home because it's on a nfs client
but it is very strange that on some machines in sol8 or sol9, it worked
without "prune option"!?

gerard henry