From: John Horne (J.Horne@plymouth.ac.uk)
Date: Fri Jun 21 2002 - 10:51:29 EDT
Hello,
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.
Anyone any ideas? I'll try and investigate a bit further, but I'm getting a
bit stumped with it. gupdatedb itself is a shell script which calls gfind.
The script itself seems okay, so I may have to try using truss with gfind to
see what happens.
BTW, gupdatedb works fine on our Solaris 7/8 systems.
Thanks,
John.
------------------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: jhorne@plymouth.ac.uk
PGP key available from public key servers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:30 EDT