Does existing RHEL 32-bit library (glibc & libstdc++) needed to be upgraded while upgrading WAA to a 64-bit environment?

Does existing RHEL 32-bit library (glibc & libstdc++) needed to be upgraded while upgrading WAA to a 64-bit environment?

Customer's environment: (e.g)
1. OS for WebALARM Agent (WAA): RHEL 5.5 64-bit
2. Current WAA version: V3.5
3. Upgrade current WAA version to V4.3.1

Question: 
Does existing RHEL 32-bit library (glibc & libstdc++) needed to be upgraded while upgrading WAA to a 64-bit environment?

Answer:
glibc & libstdc++ 32-bit library are not required to be upgraded prior to WAA upgrade on a 64-bit environment. 

More information:
N/A
    • Related Articles

    • [ARWare]: Does ARWare V3 support Windows 32-bit?

      Product Version: ARWare V3 Product Component: ARWare Client Question: Does ARWare V3 support Windows 32-bit? Answer: No. The current version does not support fresh installation on a machine with Windows 32-bit. However for an existing ARWare Client ...
    • Does WebALARM requires root privileges to run in Linux environment?

      Question: Does WebALARM requires root privileges to run in Linux environment?   Answer: Yes. Under UNIX environment, 'root' privilege is required by WebALARM for its operation to access files owned by various owners in the local filesystem. In ...
    • WAA - Tampered file related FAQ

      Customer Environment: OS for WebALARM Agent (WAA): Linux   Question(s) & Answer(s):   Q1: What is the directory for tampered file in WA(Linux)? A: "/usr/local/wa4/wa.err/" Q2: Does the tampered file format would be changed once it is copied into the ...
    • WAA's SMTP server specification method

      WAA Version: 4.3.X OS: Linux and Windows   Q1: How can I configure multiple SMTP servers to WAA with WAC?  Answer: You can only set one SMTP.  Q2: How to specify the listening port number of the SMTP  server other than the default 25.  Answer: - ...
    • How to stop WAA Real-time Monitoring?

      Question: How to stop WAA Real-time Monitoring?   Customer Environment: 1) OS for WebALARM Agent (WAA): Linux 2) WebALARM (WA) version: v4.3.X   Answer: Refer to the manual workaround below: Boot options to set the /usr/local/wa4/wa --port=8079 ...