Well, I'm not trying to beat a dead horse. I don't know what you don't understand about +"The Leopard version of WHAT? 310locate ? /usr/libexec/locateupdatedb ? Let's not even go there."+ It is very difficult to understand made up terminology such as +"On a single-user machine, that's crippling, especially if you have multiple accounts for different purposes."+ The operating system is designed so that a user's "user land", home folder (directory), is supposed to be PRIVATE and not revealed to any other users, whether it is a login user or it is in your terminology a "unix user". As I said originally posted, +"It's a good idea NOT to run- /usr/libexec/locate.updatedb from your shell or another application."+ What happens is your ENVIROMENT is used in the locate.updatedb shell script thus revealing files in your home folder (not a good idea) to any user on the system.
At least to try to bring this back to "on topic", the OP is using the wrong tool, like using a hammer to drive a screw. It can be done but it is very messy. What sould be done is consult the bill of material file left by the installation and use that to remove the application and any supporting files. Plus, any usual suspect files in /Library and ~/Library.
