Except for the problem that the Tomcat users home directory is /usr/share/tomcat5 which it doesn't have enough permission to create a '.m5' folder in when you run 'mvn package'.
Re-configuring the Tomcat home directory will more than likely break Tomcat. Guess you need a dspace user to build dspace with and then run everything under Tomcat after it's built. Or create a '.m5' directory manually with the correct permissions. -----Original Message----- From: Mark H. Wood [mailto:[email protected]] Sent: February-04-10 7:49 AM To: [email protected] Subject: Re: [Dspace-tech] DSpace 1.5.2 cocoon.log access problems (continued) On Wed, Feb 03, 2010 at 02:12:38PM -0800, Eric Schewe wrote: > Does anyone have any idea how to get DSpace and Tomcat to be > accessible by each other when Tomcat is run as 'tomcat' and DSpace is > run as 'dspace'? > > Should I just re-configure DSpace to run as the 'tomcat' users? That's what I would do, unless you have some reason for the separate accounts. DSpace doesn't care what its account is named, and Tomcat will be easier to live with if you just let it own everything it touches. -- Mark H. Wood, Lead System Programmer [email protected] Friends don't let friends publish revisable-form documents. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
