Hello, Am 30.10.2007 um 10:48 schrieb Robert Roggenbuck:
> Missing packages... this can well be. Because I did not installed > the Ubuntu package tomcat5.5 with all it's dependencies. Instead I > downloded the apache-tomcat-5.5.25.tar.gz from Apache (http:// > tomcat.apache.org/download-55.cgi). The reason was that DSpace > needs to run Tomcat as user dspace. Oh, I would strongly vote for using the distribtutions packages. The name 'dspace' for the unix system user in the install docs is just an example and I am not sure whether it is chosen luckily. But an install guide is already a long and complicated document, so they chose something that might make sense as an example on a ma- chine that does nothing else, but in fact mixes up ser- vice and app or function or whatever you call it. The reason why to use the distribution packages is that you chose the distribution to get support for upgrading your system during production. You loose the most valua- ble aspect of the distribution if you depart from this. Regarding the unix user names it depends on your think- ing what you name it. I would not change the name that debian uses. I started with 'tomcat' as the unix user when I installed by hand for the first time, but later changed to the preexisting 'www' which was present and used for apache which has the same requirements in terms of security and I replaced apache and run tomcat standalone on port 80 (which requires more packages, specifically the commons-daemon, which starts a jsvc process that runs as root and can take on a privileged port below 1024, then starting tomcat under the unprivi- leged user www). To not further confuse you, am used to debian but I run dspace on Mac OS X, but I, which explains why I dont use aptitude to install tomcat - it is not available on Mac OS. It is much more important to understand what the unix user actually needs access to. First, the database user dspace is separate from the unix user dspace. As the database user dspace is only used for the database dspace, the name makes sense. The database itself runs under another unix user 'postgres' btw. Then, the unix user under which tomcat runs will write into your dspace directory. It is obvious with the assetstore subdirectory, but is also true e.g. with the history subdirectory and others. Once running, you will see by file-dates which are written during operation. The short solution is that you run your ant tasks under the unix user which is tomcat-55 in your case. For consistency, I would make it a habit, but it is actually required only during the fresh-install. Subsequent ant updates can be run under your user as long as you are allowed to put stuff into the webapps. Your .war files get unpacked by tomcat, so the resulting subdirectory under webapps will be owned by tomcat-55 again. You should check this to get a better understanding of what is actually happening. I learned these details only after my first successful install, but I bet you are better of if you do it right from the start. Again, there is a good description how to run dspace on debian in the wiki. I would suggest that you follow it and tell us which step fails for you. Bye, Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
