Install as root on Linux - mucks up permissions?
RHEL 5
RC4 When I install RC4 as root it appears to set no permissions for world and group. As a result, other users are unable to run repotool and other commands. Is this a bug or is it not advised for root to install Jazz? Cheers, Bryan |
7 answers
On Tue, 10 Jun 2008 16:17:57 +0000, bmiller wrote:
When I install RC4 as root it appears to set no permissions for world Do not install the jazz server as root. It needs to be able to write to its directories and there is no reason that it should be running as root. - Dmitry |
|
Hi Dmitry,
Thank you for the response. I am only installing it as root as DB2 wants to be installed as root. I will try a two phase approach - installing DB2 first as root and then RC4 as the jazz user. -Bryan |
|
Well I tried installing Jazz as root and it hurled and gave me this error:
$ ./install -input install-server.xml --launcher.ini silent-install.ini Administrator privileges are required. 00:00.70 ERROR com.ibm.cic.agent.internal.application.HeadlessApplication run Administrator privileges are required. so I guess that shoots down that theory - or is there something I am missing? Cheers, Bryan |
|
I guess I am not reading very carefully. In the Getting Started docs
https://jazz.net/downloads/RationalTeamConcert/milestones/1.0RC4?p=install.docs/install_standard#dqx1t_s_server_installation_im it says, "Note: You must have administrator privileges to run the installer." Sorry for the bother. Cheers, Bryan |
|
Back to the original premise. Installing as root mucks up permissions. Now, only root can perform activities like editing teamserver.properties file and running repotool. It would be great if these files were expanded with permissions beyond just root (permissions not necessarily ownership).
-Bryan |
Bryan,
That is not entirely accurate. The default behavior of IM requires that you run it as root (and is generally recommended). However, there is a way to override this by passing in the "-isAdmin" option. This is documented in the README.txt file in the root directory of the install download. Hope that helps. -James bmiller wrote: I guess I am not reading very carefully. In the Getting Started docs |
|
In general, the installation manager is designed around the model that
you install as root and run as a normal user. However, in the case of the server, as you observed this isn't currently possible since it writes to its install location and there are files in the install location that will likely need to be modified to configure your server. You have a few options: 1. Install as root and configure / run as root. 2. Install as non-root using the -isAdmin option I mentioned in my previous reply (which will install any files that previously went in locations requiring root permissions to be placed in folders relative to the user's home directory). 3. Install as root and then set the group and group write permissions on all the files in the install location to allow it to be run by another user who is a member of the group (or even a particular user if you want to change the ownership altogether). That said, this could obviously be improved both on the documentation and install side. Please open a work item describing the issues so we can make sure this tracked. -James bmiller wrote: Back to the original premise. Installing as root mucks up |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.