If using run-in-place, do not use sudo with comp --install.
"sudo comp --install" is required for run-installed systems, because
your user does not have permission to modify system files, and installed
systems put realtime components in a system directory.
With a run-in-place system, the same user who built emc has permission
to modify the directory where realtime components are placed, so sudo is
not necessary.
The reason that 'sudo comp' prints 'command not found' is that 'sudo'
sanitizes the PATH, removing the directory added by ".
scripts/emc-environment". This is documented in the sudo manpage:
There are two distinct ways to deal with environment variables.
By default, the env_reset sudoers option is enabled. This causes
commands to be executed with a minimal environment containing
TERM, PATH, HOME, SHELL, LOGNAME, USER and USERNAME in addition
to variables from the invoking process permitted by the env_check
and env_keep sudoers options. There is effectively a whitelist
for environment variables.
Jeff
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
