Because DSpace and Tomcat on my servers are only used for DSpace, I
cheat (and do something that is not recommended practice): I have both a
DSpace user and a Tomcat user in*//*/etc/password (and in /etc/shadow)
with the same user and group identification numbers (the UID and GID).
The entries look like this in /etc/password):
dspace:x:232:232::/home/dspace:/bin/ksh
tomcat:x:232:232::/var/lib/tomcat:/bin/bash
That allows a DSpace log in (which I use for things like administrative
tasks and loading data files (which I invoke with su - dspace). Tomcat
never is used for anything stand-alone, so it doesn't matter as far as
the system is concerned (and saves a lot of fiddling around with who
owns what, when, why, and how). My systems all use KornShell (ksh), not
BASH, which doesn't matter to either DSpace or Tomcat.
Now, I did hold my nose and cross my toes when I did this (it really,
truly, is not good practice), but it works just fine and it's specific
to DSpace only (Tomcat is not used for anything else and probably never
will be on these servers). No problems with PostgreSQL, no problems with
DSpace, everything just works.
Hope this helps some.
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
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
