1 Reply Latest reply on Dec 18, 2007 6:43 PM by Bill Robinson

    getting user environment when running nsh commands

      We were trying to run some CIS Compliance Jobs, and were getting an error "ifconfig: command not found". Doing some research, we couldn't execute the command in NSH using nexec either. We did a "nexec -e set" against the remote host, and were seeing SUDO variables in there of one of the admins here.

       

      After some troubleshooting, we found out that the customer installed & started the agent on RedHat using sudo. This caused the nsh to run everything with their inherited environment, which did not include /sbin in $PATH (commands like ifconfig would not run). There needs to be documentation that says do not install the product using sudo, but as root.

       

      Just a heads up.