Hi Mark, I'm very open to changing the docs in this area starting with 6.0. You are obviously correct that, in the end, we don't need to be telling folks to create a "dspace" user acct. They can if they wish, but they also can simply just use whatever user acct tomcat runs as (often "tomcat" but not always).
We'd just need to start thinking about how to clarify this in the Install documentation, and also avoid mentioning a 'dspace' user by a specific name elsewhere in the documentation. - Tim On 6/12/2015 10:39 AM, Mark H. Wood wrote: > We still occasionally confuse a new DSpace user with this. The > documentation jumbles up installation of Tomcat with installation of > DSpace, which are separate issues. > > Case 1: user installs Tomcat using his OS' package manager, which is > natural and simplest. The package manager will set up a user account > for Tomcat, and set ownership of Tomcat's files to make it work. > After that, the user has to change all that, as well as Tomcat startup > scripts, if he wants to use the "dspace" account *which is created > later in the procedure*. This is rather error-prone and completely > unnecessary -- DSpace doesn't know or care what OS user owns its files. > > Case 2: user installs Tomcat from source. Since this requires expert > knowledge of how the user's host manages services, the user shouldn't > have any trouble writing down the name of the account he created > during this step. It is not necessary for DSpace to intrude here; > this is just setting up prerequisite software. Get the container > installed and running first, then proceed to DSpace installation. > > Case 3: user already had Tomcat and is just adding a DSpace instance > to it. The account name is already established, and we should not > breathe the slightest hint that it should be changed, as that will > likely break multiple production webapp.s unrelated to DSpace. > > In each case there is no reason to suggest a username. The DSpace > tail should not wag the Tomcat. [DSpace] and everything under it > should be owned by the account which was already created to run the > container before the user even began installing DSpace. How do I know > what that account is? Case 1: the installation process told you, or > read the package's documentation or its startup scripts, or ask your > distro. Case 2: you already know, because you selected it. Case 3 is > really either Case 1 or Case 2. > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > ------------------------------------------------------------------------------ _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
