[ http://jira.dspace.org/jira/browse/DS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Donohue updated DS-473: --------------------------- Priority: Minor (was: Major) Assignee: Mark Wood >From discussion during DSpace Developers Mtg on Feb 17 2010 ( >http://www.duraspace.org/irclogs/index.php?date=2010-02-17 ) Assigned this issue to Mark Wood. He'll followup with some suggestions. Sounds like this is not a DSpace bug per say, but has more to do with system administration. [15:49] <tdonohue> http://jira.dspace.org/jira/browse/DS-473 : cocoon.log permissions seem incorrect [15:49] <kshepherd> ds-473 looks like a 'linux system administration' issue to me :P [15:50] <tdonohue> yea, I was just going to say that [15:50] <tdonohue> -1 : mark not a bug -- followup with help/suggestions? [15:50] <mhwood> I agree. Tomcat expects to own the stuff it touches and it's very difficult to get around that. Maybe the submitter could handle this with Posix ACLs? [15:51] <tdonohue> anyone want to follow up with him, give a few suggestions, and close this? [15:51] <kshepherd> yes, ACLs offer much more than the simple user/group modes [15:51] <mhwood> I can follow up. [15:51] <kshepherd> however, just changing tomcat's umask in /etc/bashrc or whatever will do it [15:51] <tdonohue> DS-473: Assign to mhwood to followup. Can be closed after followup [15:51] <kshepherd> (cause new files to be 664 instead of 644) > cocoon.log permissions seem incorrect > ------------------------------------- > > Key: DS-473 > URL: http://jira.dspace.org/jira/browse/DS-473 > Project: DSpace 1.x > Issue Type: Bug > Components: XMLUI > Affects Versions: 1.5.2 > Environment: Redhat Enterprise 5.4 64-bit, Tomcat 5.5.23, > Reporter: Eric Schewe > Assignee: Mark Wood > Priority: Minor > > I am using a local account called 'dspace' for building and deploying DSpace > and Tomcat is running as 'tomcat'. I've added 'tomcat' to the 'dspace' group > and made sure my DSpace installation directory has at least 770 (rwxrwx---) > permissions so dspace and tomcat can access the files. This appears to be > working just fine. The only problem I'm running into is getting dspace access > to cocoon.log. The log file is created by Tomcat, the permissions are 644 > (rw-r--r--) and it's owned by tomcat:tomcat. Whenever any of the dspace > cronjobs are triggered they fail because they can't read/write to cocoon.log. > I'm not sure if this is a Tomcat issue or a DSpace issue (or if this is even > a bug or an error on my end) but would it be possible to make it so the > cocoon.log file is created with atleast 660 (rw-rw-r--) permissions so in > this kind of a configuration dspace and tomcat can share the file? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel