On Wed, Jun 05, 2013 at 09:59:04AM +0200, Hilton Gibson wrote: > Hi Tim I'm not Tim, but here's my 2ยข worth anyway.
> When creating the "dspace" user and then assigning this user the Tomcat6 > account, how do we deal with file permissions needed by Tomcat6 for the > following system files; > *dspace@ir1:~$ dpkg -L tomcat6* > */.* > */usr* > */usr/share* > */usr/share/doc* > */usr/share/doc/tomcat6* > */usr/share/doc/tomcat6/changelog.Debian.gz* > */usr/share/doc/tomcat6/copyright* > */usr/share/tomcat6* > */usr/share/tomcat6/webapps* > */usr/share/tomcat6/webapps/default_root* > */usr/share/tomcat6/webapps/default_root/index.html* > */usr/share/tomcat6/webapps/default_root/META-INF* > */usr/share/tomcat6/webapps/default_root/META-INF/context.xml* > */var* > */var/cache* > */var/cache/tomcat6* > */var/log* > */var/log/tomcat6* > */var/lib* > */var/lib/tomcat6* > */var/lib/tomcat6/common* > */var/lib/tomcat6/common/classes* > */var/lib/tomcat6/server* > */var/lib/tomcat6/server/classes* > */var/lib/tomcat6/webapps* > */var/lib/tomcat6/shared* > */var/lib/tomcat6/shared/classes* > */etc* > */etc/init.d* > */etc/init.d/tomcat6* > */etc/tomcat6* > */etc/tomcat6/context.xml* > */etc/tomcat6/web.xml* > */etc/tomcat6/logging.properties* > */etc/tomcat6/policy.d* > */etc/tomcat6/policy.d/02debian.policy* > */etc/tomcat6/policy.d/50local.policy* > */etc/tomcat6/policy.d/03catalina.policy* > */etc/tomcat6/policy.d/01system.policy* > */etc/tomcat6/policy.d/04webapps.policy* > */etc/tomcat6/catalina.properties* > */etc/tomcat6/tomcat-users.xml* > */etc/tomcat6/Catalina* > */etc/tomcat6/Catalina/localhost* > */etc/tomcat6/server.xml* > */etc/cron.daily* > */etc/cron.daily/tomcat6* > */etc/default* > */etc/default/tomcat6* > */usr/share/doc/tomcat6/README.Debian.gz* > */var/lib/tomcat6/conf* > */var/lib/tomcat6/work* > */var/lib/tomcat6/logs* If your servlet container (e.g. Tomcat) already has an account, that account should own the DSpace files. You only need to create a user "dspace" if you are installing Tomcat from source and can't decide what to name its account. (In that case I would name it "tomcat" and let the DSpace files be owned by "tomcat". There's nothing significant about a user named "dspace".) Anyway, whatever owns Tomcat should own DSpace and vice versa. If your distribution creates an account when installing Tomcat, use that for DSpace as well. Trying to make it work with two separate accounts is painful and unnecessary, as is trying to rejigger Tomcat to run as a different account than what your package manager used to install it. The DSpace documentation seems to assume that you are installing all prerequisites by hand and have no other use for Tomcat. I've schemed to remold that section but haven't yet found an acceptable way to get rid of this confusing "dspace" user. I continue to watch it from the shadows, devising strategems.... -- Mark H. Wood, Lead System Programmer [email protected] Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________ 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
