Bug 21535

I discovered the problem first tonight when doing a 'locate portsentry.conf'
which resides in /usr/local/psionic/portsentry.  When I did a locate it 
didn't come up with the filename.  I was however able to find it by
doing find '/ -name portsentry.con -print'.

I then took a close examination of what shell was being used for the 
script ( sh ) and that nobody indeed was running
properly and that the cron was setup correct etc... cron shell
ok etc.

I then completely removed the /var/db/locate.database.  I then 
procedded to initate the update by hand, by touching the db file, 
then chowning, chmoding, and setting the perms to 644 as indicated 
by the  310.locate script.

I then ran ( by hand ) 'echo /usr/libexec/locate.updatedb | nice -5 su -fm nobody' 
and the system proceeded to initialize the rebuild of the database.

I then checked to ensure a new database file was indeed back in 
/var/db.. and it was.

I then did another 'locate portsentry.conf' and it WAS not in
the database.... However.. almost every other file on the
system was in the database.. that is to say files within
the root path.

I then started to look for files that would pertain to locate's path and
came up with /etc/locate.rc.  The path defined there was '/' which
simply tells me that it will search the tree '/' down.

Then I tried something else. I simply ran, by hand /usr/libexec/locate.updatedb.
( without nice ). The database once again began to build.  After it was built,
I , again did a 'locate portsentry.conf' and guess what ? It found
it exactly where it was supposed to be in /usr/psionic/portsentry !.
(portsentry.conf)

With this knowledge in hand, I then edited 310.locate to reflect the
command /usr/libexec/locate.updatedb without args, then ran 
'period weekly' again and the entire system was then completely
databased.

This is happening on 2 seperate systems, completely unrelated to 
each other.. and I'm sure it has to do with a path configuration
problem.

Fix: 

The only way I have found to fix the problem is to remove;
'echo' from the beginning of the command and to remove
'| nice -5 su -fm nobody' from the end of the command, leaving
the binary to run simply as /usr/libexec.updatedb in 301.locate.
How-To-Repeat: 
Place a file in /usr/local/psionic/portsentry and run periodic weekly
with the 'out of the box' args for updatedb in 301.weekly either by
hand or from the cron.  Makes no difference either way.

Have I stumbled onto something here.. or am I just not
working updatedb properly by not placing the correct paths in 
/etc/locate.rc ??