You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/03/11 21:22:41 UTC
[Bug 295] New - Config files with Multiple User IDs BugRat Report#546
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=295
*** shadow/295 Sun Mar 11 12:22:41 2001
--- shadow/295.tmp.23739 Sun Mar 11 12:22:41 2001
***************
*** 0 ****
--- 1,27 ----
+ +============================================================================+
+ | Config files with Multiple User IDs BugRat Report#546 |
+ +----------------------------------------------------------------------------+
+ | Bug #: 295 Product: Tomcat 3 |
+ | Status: RESOLVED Version: 3.2.1 Final |
+ | Resolution: LATER Platform: All |
+ | Severity: Normal OS/Version: All |
+ | Priority: High Component: Servlet |
+ +----------------------------------------------------------------------------+
+ | Assigned To: tomcat-dev@jakarta.apache.org |
+ | Reported By: tomcat-bugs@cortexity.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ I am running Tomcat on a UNIX-like (LINUX) server and have a practice of having one user ID (softowner) that is the owner of the Tomcat configuration files, class files, and application libraries. In general any file that doesn't need to be modified by the running application. I use another ID (dataowner) as the effective user of the running server. This owns the data files and work files.
+
+ As Tomcat 3.2 works I can give dataowner write access to webapps/work, I give softowner write access to webapps, webapps/classes, webapps/lib, webapps/htdocs , etc.
+
+ My problem is that I both softowner and dataowner need write access into the config directory because the program creates config files as the server starts. but softowner needs write access to work with othe config files.
+
+ I would like to have a way to suppress generation of config files or explicit invokation of the capability. I also want better seperation between what the running program needs write access to and what it only needs read access to.
+
+ ------- Additional Comments From marc.saegesser@apropos.com 2001-03-11 12:22 -------
+ Sounds like a good idea. It won't make it into 3.2.2, but we should look at
+ this for 3.3 and later.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, email: tomcat-dev-help@jakarta.apache.org