SUMMARY: gupdatedb fails - Solaris 9

Many thanks to those who replied to this:

 david.markowitz@xxxxxxxxxxxxxxxx
 Marty Leisner <mleisner@xxxxxxxxxxxxxxxx>
 George.R.Goffe@xxxxxxxxxxx

As George Goffe pointed out he had had problems with those odd directories
/net and /xfn. I found that if I cd to them and did an 'ls -l' then it
returned nothing, in fact didn't return, the machine just sat there.

Suspecting that something was wrong (you think!?) I rebooted the system. The
/net and /xfn directories now appear okay when being listed and
gupdatedb/gfind works fine.


Regards,

John.

PS.
Having said that I now find that if I insert a cdrom in the drive then it
doesn't get automounted! From Sunsolve it seems others have had this problem
with Solaris 9 and the workaround was to add a line to /etc/rmmount.conf
(bug id 4531636 has details; 4638163 the workaround (I think)). Anyway, it
still doesn't work so I have raised this with Sun. Stopping vold and
manually mounting the cdrom seems to work. So beware.



Original message:

Anyone using the /opt/sfw/bin/gupdatedb program on Solaris 9? If I run the
command:
  gupdatedb --localpaths=/usr/local 
 
it works fine. The command finishes within a few seconds (/usr/local is
small at the moment), and produces a database file in /opt/sfw/var. (Note
I had to create /opt/sfw/var manually since the sun installation didn't.)
 
However, if I run:
  gupdatedb --prunepaths="/proc /tmp"
 
so the localpaths should default to '/', then the program seems to run a
bit (from watching 'top'), and then sort of fizzles out! The cpu usage of
gfind/sort goes down to zero. The file /opt/sfw/var/locatedb.n is created
but of 0 length, and the command itself does not finish.
--------------

------------------------------------------------------------------------
John Horne, University of Plymouth, UK           Tel: +44 (0)1752 233914
E-mail: jhorne@xxxxxxxxxxxxxx
PGP key available from public key servers