The default license file includes a license key for the HP Eloquence Personal Edition. Please request a new permanent license key using the form included with the delivery or refer to the HP Eloquence web site at URL http://www.hp-eloquence.com/license.
HP Eloquence for the Linux platform is available in separate packages for libc6 (also known as glibc2) and libc5 based systems.
libc.so.6 (glibc-2.0.6) libm.so.6 (glibc-2.0.6)For distributions using a newer version of the glibc library such as SuSE 6.2 and above or Red Hat 6.x and above you may need to install backwards compatible library versions.
HP Eloquence provides its own copy of the following libraries in the /opt/eloquence6/lib directory:
libncurses.so.4.2 libstdc++.so.2.9Those libraries have been included to solve compatibility problems with various Linux distributions providing prossibly incompatible versions of those libraries.
libc.so.5.4.33 libm.so.5.0.9Earlier versions of those libraries are likely to cause problems. For example the libc.so.5.3.12 included with old Red Hat distributions does notwork with HP Eloquence and causes random failures.
HP Eloquence provides its own copy of the following libraries in the /opt/eloquence6/lib directory:
libncurses.so.3.0 libstdc++.so.2.9Those libraries have been included to solve compatibility problems with various Linux distributions providing prossibly incompatible versions of those libraries.
Please note that this build has received less testing and we recommend to use the libc6 build for glibc2.1 and glibc2.2 based distributions.
If you have trouble getting HP Eloquence working reliable on a glibc2.1 or glibc2.2 based distribution you may want to try the glibc2.1 build though. Please send us a messsage at feedback@hp-eloquence.com if it makes a difference for you.
Please make sure that at least following shared library versions are installed:
libc.so.6 (glibc-2.1.2) libm.so.6 (glibc-2.1.2)For distributions using the glibc 2.2 library such as SuSE 7.x and Red Hat 7.x and above you may need to install backwards compatible libraries.
HP Eloquence provides its own copy of the following libraries in the /opt/eloquence6/lib directory:
libncurses.so.4.2 /usr/lib/libstdc++-libc6.1-1.so.2Those libraries have been included to solve compatibility problems with various Linux distributions providing prossibly incompatible versions of those libraries.
HP Eloquence A.06.31 has been compiled with egcs-1.1.2 for the glibc versions and egcs-1.1.1 for the libc5 version.
We do not recommend to use early Linux 2.4 kernels (before version 2.4.6) in production environments.
For new installations, a recent glibc based distribution (such as SuSE 7.x or RedHat 7.x) is recommended.
Future HP Eloquence release are likely to no longer support libc5 based systems and Linux kernel versions below 2.2.
Please check the HP Eloquence web site for updates and patches.
To install HP Eloquence execute the command below:
rpm -i B1368B-A.06.31.libc6-*.i386.rpmTo update an existing HP Eloquence installation, please shut down HP Eloquence and execute the command below:
/etc/init.d/eloq6 stop rpm -U B1368B-A.06.31.libc6-*.i386.rpm /etc/init.d/eloq6 start
/sbin/init.d/eloq6 stop rpm -U B1368B-A.06.31.libc6-*.i386.rpm /sbin/init.d/eloq6 start
/etc/rc.d/init.d/eloq6 stop rpm -U B1368B-A.06.31.libc6-*.i386.rpm /etc/rc.d/init.d/eloq6 stop
The new license key can be requested by either submitting the Form enclosed with your software update or on-line at the HP Eloquence web site: http://www.hp-eloquence.com/license.
Please comment out the previous license key when adding the new A.06.31 license key to your license file /etc/opt/eloquence6/license. Otherwise the new license may not be recognized and chklic might output the following messages:
A.06.20: Bad license key revision. Duplicate sequence number: Ignoring license
cp /opt/eloquence6/newconfig/config/license /etc/opt/eloquence6/license
New startup config options:
# The following settings are related to starting HP Eloquence # automatically during system boot. # # Start HP Eloquence daemons? ("yes" or "no") START_ELOQ="yes" # # The following settings allow specifying startup for specific # daemons and daemon commandline arguments. They are all optional. # # Set START_ELOQSD to 1 to start the eloqsd daemon. #START_ELOQSD=1 #ELOQSD_ARGS="" # # Set START_ELOQDB6 to 1 to start the eloqdb6 daemon. #START_ELOQDB6=1 #ELOQDB6_ARGS=""
The solution is to use a larger block size for the ext2 filesystem which holds the database.
Classical UNIX file systems are usually organized in blocks. The file system block size can be choosen at file system creation time (eg. on Linux by using the -b 4096 command line argument to mk2efs would result in a 4KB block size). For the Linux ext2 file system, the default block size used to be 1 KB for older distributions. The current mk2efs uses a block size of 4 KB.
In order to maintain your data on the disk, the operating system
maintains additional information where your data is located on disk.
When files get bigger so does the overhead to keep track where your
data is located.
Enlarging the file system block size greatly reduces the amount of
overhead required to maintain your data if you use big files (as
eloqdb6 does) at the expense of using slightly more disk space for
small files.
In addition to the data blocks (holding the file contents) additional information is maintained where the data blocks are actually located on the disk. When the file size exceeds a trivial size, the location of the data blocks is also maintained in a separate block on disk (indirect blocks - which the OS also needs to keep track of). At some point (depending on file size and block size) you need blocks that specify the location of blocks that specify the location of your data on disk (double indirection). At this point maintaining this information becomes a factor when reading or writing the database.
While a block size of 8 KB would be a "perfect fit", the max. usable block size depends on the architecture (processor). On the x86 this is 4 KB. We recommend to specify a block size of 4 KB for the Linux platform to create a file system dedicated to hold your database.