> Is there some reason you want the account to be named "dspace"?
> DSpace doesn't care, and never logs in. DSpace only needs to have its
> files accessible by Tomcat, and the simplest way to do that is to have
> them owned by the same account that runs Tomcat.
Only because I'm working my way through the installation instructions
and got to the point that adds an account for dspace (which, of course,
indicates that it needs to be the same UID as Tomcat. You know, the
installation runs from pp. 39-67 and I'm taking one step at a time on a
clean install of Slackware 14.0 (with patches applied). Hit the
instruction that says "create the dspace user," so I create the dspace
user (this is a few pages after installing Tomcat and making sure that
it works; i.e., I can start it in a browser and get the "It Works"
message). Just a little confusing when you see "create the dspace user"
and then start thinking about two users with the same UID and stuff like
that.
>
> DSpace is just one of the things Tomcat is doing in its own address
> space. So Tomcat needs a user identity but DSpace doesn't. If you
> let the DSpace files be owned by the account that the Tomcat
> installation created, it works. If you change the account name, you
> will probably have to reconfigure the Tomcat startup script, and make
> sure it doesn't get unreconfigured when Tomcat is upgraded some day.
Following the instructions at this point I have, in /etc/passwd, two
accounts:
tomcat:x:232:232::/var/lib/tomcat:/bin/bash
dspace:x:1001:1001::/home/dspace:/bin/bash
So, I gotta wonder why there's a dspace account; tomcat can own all the
dspace files, that's no problem, but why the heck is there a separate
account (that wants to be the same UID) -- that's where the confusion
lies. Unix-like systems really don't like multiple users with the same
UID. I can simply chown all the dspace files to 232 (in this case) and
be done with it but there's that nagging question.
>
> DSpace is told in its configuration where it lives and doesn't depend
> on the OS for such knowledge. OTOH I don't know whether Tomcat makes
> use of its "home" directory and would be reluctant to change it.
I think the rule for tomcat is that you leave it alone 'cause the
browser can find it by the port.
I've looked further at the configuration file and I'm probably going to
put the dspace files in /opt and symlink where necessary (I usually
install "optional" software, things like OpenOffice, in /opt so it'll
live in /opt/dspace unless there's a real good reason to stick it in the
/usr tree -- which I try to avoid).
>
> You're correct that DSpace should not be installed inside Tomcat. Put
> it in some other convenient place. Only the webapp.s that you intend
> to use need to be known to Tomcat, and are typically copied from
> [DSpace] to wherever Tomcat's webapps/ directory is.
I'm pretty sure that tomcat points at /var/lib/tomcat (with links to
/etc) but I wouldn't bet the farm on that -- I've never used tomcat and
still have a learning curve to contend with. Oddly, Linux Journal has a
good introductory article about tomcat in the current (July) issue.
Worth a read.
Thank you for taking the time and trouble to help out.
Thomas
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
