REPOSTED FOR NON-MEMBER ADDRESS: Arie van Dam [EMAIL PROTECTED]
[Bounce notice: Eugene, Your recent post to our lists bounced
because either you are not a member or because you are not signed up
using the e-mail address which you used to post. To subscribe or
resubscribe please visit
Thanks to all that replied!
Licensing isn't an issue. If we need to reconfigure our licensing scheme
and/or purchase more licenses, we will.
My larger concern is any of those extraneous files out in the wonderful world
of unix. Doing a central install doesn't do us much good if there are files
Talk to you supplier about backup server licensing. There are a couple of
options for licensing UniVerse on a backup server. One scenarios that had
previously been offered is for one license on the hot site and when the
other fails you up the license on the backup server. The second option was
There are files at the root filesystem: /.uvhome /.unishared /.uvdlls
The spooler typically installs into: /usr/spool/uv
The spooler area could be moved elsewhere if you modify
uvhome/uvconfig
I think that might be it, including the files that start UV
(/etc/inittab) or /etc/init.d
To be sure, I would take a snapshot of the system before the install, then
another after the install and do a diff on the to snaps. That should tell
you the story.
Like so.
cd /;find . -print /tmp/file_list_b4_uv_install
Install Universe
cd /;find . -print
I'd recommend installing UniVerse on a static file system on each server
independently. Your data files are on a mountable file system on the RAID or
SAN.
Safe / robust - and it would avoid some of the issues you may hit with the
new UniVerse licensing model in 10.2. Please check whether you need
