Kbase P122234: Is the "su" command valid for becoming the root user id prior to installing Progress?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/04/2008 |
|
Status: Verified
GOAL:
Are there any issues that could arise from running the Progress install (proinst) not logging in as root but doing a "su" to root?
GOAL:
Is it acceptable to su root and perform and installation of Progress?
GOAL:
Do I have to login as root to perform and Progress installation?
GOAL:
Can su be used to assume root for the purposes of installing Progress?
FACT(s) (Environment):
UNIX
Progress/OpenEdge Versions
FIX:
The su (set user or super user) command allows a user to become another user without logging out.
The su command executes a new shell with the real and effective user id being consistent with that of the specified user. Commands then ran within this shell are executed with the new user's privileges. However, the environment is still based off the original users environment with the exception of $PATH, $PS1. The environment variables for $HOME and $ENV are removed. This is because the shell being initiated is a subshell of the existing environment. The new userid you are suing will not have gone through the login process.
Command syntax:
su userid
Example: su root
If you use the (-) hyphen option to the su command, then the new shell is initiated as if the user had logged into the system originally. The login scripts associated with the new userid are executed and configure the environment to that of the new userid being specified. This includes $HOME, $PATH and $PS1.
Command syntax:
su - userid
Example: su - root
A recommendation would be to issue the (-) hyphen with the su command to ensure that the environment that the Progress installation is being executed in, mimics the same environment that the root user would have when logging into the actual system.