Difference between revisions of "Installing VsrvTcp 4.9.x"

From Vital Soft Wiki
Jump to: navigation, search
>Johno
(Installation)
>Johno
(Installation)
Line 14: Line 14:
 
::* Transfer the gz file, using a binary transfer, to the /ASKPLUS directory.
 
::* Transfer the gz file, using a binary transfer, to the /ASKPLUS directory.
  
:'''# Update Permissions:'''
+
# '''Unzip and Copy the File:'''
:: * Logon to HPUX as '''root'''
+
::* Logon to HPUX as '''root'''
:: * cd /ASKPLUS
+
::* cd /ASKPLUS
 +
::* gunzip vsrvtcp_arch_ver.gz  (Your file will have a different name, for example:  vsrvtcp_it64_4219.gz)
 +
::* cp vsrvtcp_arch_ver vsrvtcp42
 +
 
 +
# '''Update Permissions:'''
 +
::* chown root vsrvtcp42
 +
::* chmod 755 vsrvtcp42
 +
::* chmod +s vsrvtcp42
 +
 
 +
# '''Check the Version:'''
 +
::* ./vsrvtcp42 -v
 +
 
 +
If the version number is correct, start VsrvTcp on a different port:
 +
 
 +
./vsrvtcp42 -a -t -n29501 > /dev/null

Revision as of 22:39, 25 July 2014

Installing VsrvTcp 4.2.x

The Visimage3 Beta requires installation of VsrvTcp Version 4.2.x.

During the beta, we recommend that you install the new version of VsrvTcp on a different port so as to minimize possible impact on your production Visimage users and jobs.

Download the latest version from the website here.

Installation

New VsrvTcp versions are distributed as individual .gz files. Each version has a unique name in the format vsrvtcp_arch_ver.gz, where 'arch' is the supported system (pa32 or it64) and ver is the version number. For example, vsrvtcp_it64_4219.gz.'

  1. Transfer the file to UNIX:
  • Transfer the gz file, using a binary transfer, to the /ASKPLUS directory.
  1. Unzip and Copy the File:
  • Logon to HPUX as root
  • cd /ASKPLUS
  • gunzip vsrvtcp_arch_ver.gz (Your file will have a different name, for example: vsrvtcp_it64_4219.gz)
  • cp vsrvtcp_arch_ver vsrvtcp42
  1. Update Permissions:
  • chown root vsrvtcp42
  • chmod 755 vsrvtcp42
  • chmod +s vsrvtcp42
  1. Check the Version:
  • ./vsrvtcp42 -v

If the version number is correct, start VsrvTcp on a different port:

./vsrvtcp42 -a -t -n29501 > /dev/null