[tangent alert!]
Here for some time now we've been running with [DSpace] split into two
areas on different volumes. Stuff that changes seldom, such as code
and configuration, is in /opt/SITENAME, while volatile stuff (logs,
reports, full-text index data, etc.) are in /var/lib/SITENAME. In
instances which are sufficiently new to do config. variable
substitution, I've introduced a new "dspace.var" variable and edited
all the paths to volatile stuff to be ${dspace.var}/SOMETHING instead
of ${dspace.dir}/SOMETHING.
It's possible that I have an overactive system-administrator gland,
but I like having applications split up this way. Theoretically
${dspace.dir} could be mounted read-only except during upgrades or
configuration changes, for example.
I've created a separate volume for the assetstore, although it's
still mounted on /var/lib/SITENAME/assetstore.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Friends don't let friends publish revisable-form documents.
pgpAh0sIIYdUd.pgp
Description: PGP signature
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
