[ 
http://jira.dspace.org/jira/browse/DS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11461#action_11461
 ] 

Mark Wood commented on DS-535:
------------------------------

Agreed:  if there are concerns, better to delay the patch.

The source of the trouble is the assumption that the reader is deciding what 
name to give to the account which will be used to run the servlet container.  
Package managers tend to take that decision over.  In every package management 
system I'm aware of, Tomcat gets run as a user named "tomcat".  Meanwhile our 
documentation apparently gives a strong impression that one should be using the 
name "dspace".  In fact it doesn't matter what the name is, so long as the 
entity installing Tomcat and the entity installing and running DSpace use the 
same account.  People who get Tomcat installed under one account and try to use 
it under another are entering a world of pain.

If we are going to give advice specific to Tomcat, we need to convey one simple 
idea:  whatever account owns and runs Tomcat should own all the installed 
DSpace files and directories.

> Documentation patch to alleviate file ownership confusion
> ---------------------------------------------------------
>
>                 Key: DS-535
>                 URL: http://jira.dspace.org/jira/browse/DS-535
>             Project: DSpace 1.x
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.6.0
>            Reporter: Mark Wood
>            Assignee: Jeffrey Trimble
>            Priority: Minor
>             Fix For: 1.7
>
>         Attachments: installation.patch
>
>   Original Estimate: 5 minutes
>          Time Spent: 5 minutes
>  Remaining Estimate: 0 minutes
>
> A number of new users seem to have difficulty in getting file ownership and 
> permissions correct.  I feel that many new users will be installing Tomcat 
> (or whatever servlet container) using their OS' package manager, which will 
> likely create a username for it.  Our instructions to create a user 'dspace' 
> and use that will then lead some to try to change the user under which Tomcat 
> runs.  This is problematic.  The 'dspace' user is unnecessary and confusing; 
> DSpace should use the container's account.
> A suggested patch is attached.  Please discuss.

-- 
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

        

------------------------------------------------------------------------------

_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to