I can only emphasize on what RudiC already said: running sudo command is a completely different thing than running command. Basically sudo does:

1) switch to another user acount (by default this is root)
2) execute command as this user
3) switch back.

Of course, a different user can have (and most probably has) a different environment and when you change yours then his is not affected at all. It does not matter what is in your PATH, what matters is what is in roots PATH.

Try sudo echo $PATH and most probably /your/home/bin will not be included in it. If you can change it you could do that although i think it would be a bad idea.

Instead, put a script that should be run by several users (and eventually as root) in /usr/local/bin or in either /usr/local/sbin or /root/bin if it should only be run as root. Put /root/bin or /usr/local/sbin in roots PATH in this case (i suppose /usr/local/bin to be already included there). Then you can use the command you used.

I hope this helps.

bakunin

PS: you probably wonder why it works with ./command. The reason is that the "." for "current directory" is expanded by the shell even before any attempt of executing any command is made. Therefore the shell replaces "." with something like "/path/to/your/home/bin" and only then executes sudo /path/to/your/home/bin/cleanup2 so that the user you switch to doesn't have to have it in its PATH to find it.

bakunin