> > 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.
BOOM! *light bulb turns on!* Thanks a ton for this Mark. I learned this "the hard way" and never did understand the motivation until now. We happen to use a distro *cough cough* Red Hat ;-) that always overwrote the permissions on upgrade and I can now safely purge my "homegrown" scripts. -- "Beer busts, beer blasts, keggers, stein hoists, A.A. meetings, beer nights..." --Homer Simpson ------------------------------------------------------------------------------ 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
