That should only happen if you have the NOEXEC tag set for the command, if it there is a "Defaults noexec" in sudoers. I can't reproduce that problem with the Solaris 10 sudo package from http://www.sudo.ws/sudo/download.html#binary - todd