On Tue, Jul 28, 2020 at 01:57:39PM -0700, [email protected] wrote: > Thanks for your response, Mark. Do you know if how to check/update > assetstore permissions is documented anywhere?
I can't think of any place where this is documented, but it's really simple: everything in and below [dspace]/assetstore (and any additional assetstores that you may have) should be owned by the user that runs Tomcat and should grant read/write permission to that user. I ran a quick experiment on a test instance of DSpace. On this system Tomcat is run by the user 'tomcat'. I am using GNU 'find'. This command should list all files in 'assetstore' NOT owned by the user 'tomcat', *provided* that your current directory is the [dspace] directory and the assetstore is a subdirectory named "assetstore": find assetstore -not -user tomcat This command should list all files under 'assetstore' that are not read/write for the owner, regardless of other permissions: find assetstore -not -perm -600 -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/20200731142551.GC3259%40IUPUI.Edu.
signature.asc
Description: PGP signature
