Hi Gerald, > > > slocate is an rpm > > > rpm -e and rpm -i > > > replace it > > > > Done and recreated d/b and made no difference to my situation. Locate still > > produces munged output for the root user. > > > crazy! > Have you tried, turning security off > locate -l 0 some-file > l is a lower case 'L'
Still gives silly output, here's an example: locate -l 0 sendmail.php /home/sites/site5usr/lib/php/Mail/sendmail.php This server is configured the same way as 2 others with any changes duplicated across them, but only this one exhibits this behaviour. I'm sure the clue must be in the first bit which is being placed in front where the correct result of the above search should be: locate sendmail.php /usr/lib/php/Mail/sendmail.php I also recreated the database using slocate -u -v to a text file and searched the verbose output for the example file here, sendmail.php, and it appears just fine in there. So where is the /home/sites/site5 bit coming from? It's very odd. I can only guess that it's a file system problem, but it's certainly not apparent other than in slocate. I was also toying with the idea that naming a file in some strange way could confuse slocate, but I don't know where to start with that. -- Regards, Jonathan Michaelson Commercial CGI Scripting, Web Hosting Web-based Email, Homepage Creation and Live Help products http://www.webumake.com _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
