SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
DSpace is the software of choice for academic, non-profit, and commercial organizations building open digital repositories. It is free and easy to install "out of the box" and completely customizable to fit the needs of any organization.
DSpace preserves and enables easy and open access to all types of digital content including text, images, moving images, mpegs and data sets. And with an ever-growing community of developers, committed to continuously expanding and improving the software, each DSpace installation benefits from the next.
Unix-like OS (Slackware 64-bit 14.0);
Oracle JDK (6 or 7, I'm at 7u25);
Perl (optional, probably won't be used);
DSpace binary or source (I have the source).
All the above, except DSpace source) are from SlackBuilds.org or, in the case of JDK, built from the Slackware-provided SlackBuild from the /extra directory.
Now, I'm getting stupider by the hour and this one I just can't get my head wrapped around:
Note that DSpace will need to run as the same user as Tomcat, so you might want to install and run Tomcat as a user called 'dspace'. Set the environment variable TOMCAT_USER appropriately.
You need to ensure that Tomcat has a) enough memory to run DSpace and b) uses UTF-8 as its default file encoding for international character support. So ensure in your startup scripts (etc) that the following environment variable is set: JAVA_OPTS="-Xmx512M -Xms64M -Dfile.encoding=UTF-8"
There need to be two users, tomcat and dspace and, if I remember correctly, you can't have two users with the same UID, so what the heck is the "right" way to do this? I can fiddle with the Apache-Tomcat SlackBuild (making it dspace) or... I dunno what -- I'm just brain dead here.
Sure would appreciate some input from somebody that's actually done a DSpace installation or anybody that's got more smarts than me and might point in the right direction.
Looks like you create one user account (whether it is called 'tomcat' or 'dspace' or 'santa' is not relevant) and start both tomcat and dspace with that same user account. Probably the user account will be configurable in a configuration file like it is done in "/etc/httpd.conf" for apache httpd.
Hmm - I thought you can have 2 users with the same UID. You simply copy+paste the entry in /etc/passwd and modify the name entry. I know (from my work) that auditors hate that, but I do think it works.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
OK, so here's what I'm thinking -- Apache-Tomcat installs first, I don't want to mess with the SlackBuild (so I don't have to remember the lie I told when an update comes along) so build and install it with the tomcat user id and group then edit passwd, shadow and group just changing "tomcat" to "dspace." Probably going to have to change the home directory later (DSpace, I'm pretty sure, is a log in account where Tomcat is not -- it just lives in /var/lib/tomcat with symbolic links to /etc). Seems like it ought to work.
@Mark_Pettit: Yeah, I've done that (back in System 3, SVR4 and Solaris days) and, yeah, the auditors yammer at you (deservedly) about doing it, and, yup it would probably work, but... this system is going to be in use for a long, long time in an institutional setting and, well, just don't wanna do that unless I absolutely, positively, have to, know what I mean. Thanks for the thought.
Haven't had this much fun since the first time I built Apache from scratch on a Solaris box about 20 years ago. Whee!