AccuRev /etc/init.d scripts


This file contains updated and new versions of the files in ..../accurev/extras/unix. Download and run tar xvzf AccuRev-init.d-community.tar.gz to expand out the file. Then read the README file. It is also below.

Copyright (c) Micro Focus 2017
All Rights Reserved

Included in this directory are the following files:

README         - this file
accurev        - AccuRev Server start-up, where the server can be an AccuRev Master or Replica server
accurev_mqtt    - AccuRev Mosquito service / Message Queue Telemetry Transport
accurev_replica - AccuRev Replica: Create AccuRev login sessions, possibly via a SSH tunnel.
accurev_web    - AccuRev Web Service
accurevSetLinks - Script to create links in /etc/init.d to start/stop the above processes.

accurev_rlm    - AccuRev RLM (deprecated in 7.0) Reprise License Manager found

Example acserver.cnf files from an AccuRev Replica used to configure either a secure or
non secure connection to the AccuRev Master Server.

All the above /etc/init.d scripts will start up the processes to run not as root, but by the user
and group defined by the variables OS_USER and OS_GROUP.

The scripts log their output to the file /var/log/accurev/accurev.log. This is controlled by the
variables OS_LOG_DIR, which defines the directory where log files will be found and the variable
LOGFILE which is derived from OS_LOG_DIR. That allows you to override the default log location
and logfile name.

On Solaris machines user /var/adm instead of /var/log as used on Linux.

Where to find the AccuRev executable "accurev" is controlled by the variable ACCUREV_BIN

Each script has a section defined by "CUSTOMIZE ME Start" and "CUSTOMIZE ME end" in which local
site customization are expected to be made.

In the accurev_replica script different connection methods for Replicas are provide.
They are: NOT_SECURE, SSH for connections via ssh(1) and Custom. The first two are
present and working. To support a Custom connect, the customer must flush out the
functionality in the functions:AccuRevConnect_Custom(), AccuRevDisconnect_Custom(),
and AccuRevStatus_Custom().

For the SSH Port Forwarding to work in the accurev_replica script, an ssh(1) key,
that is created on the AccuRev Replica by the ${OS_USER} must be created. This is done
via ssh-keygen(1).  The public key is then copied to the AccuRev Master Server via the
ssh-copy-id(1) command. During the ssh-copy-id,you must accept machine's

The ssh(1) steps to follow to create a key and make it available on the AccuRev Master
Server are as follow below. As the Linux OS user, as definded by ${OS_USER} in the accurev_replica script
in the CUSTOMIZE ME section are as follows.

   ssh-keygen  -t ecdsa -b 521    <<<<< no passphrase <<<<<
   ssh-copy-id -i ~/.ssh/id_ecdsa acserver@AccuRevMasterServerHostName  <<<<< Accept the key <<<<<
   ssh 'acserver@AccuRevMasterServerHostName

Useful website on SSH

Place in /etc/init.d only those accurev* scripts that you need. Then use either use
accurevSetLinks to create the links from /etc/rc5.d for normal running on most Linux
machines (or other runlevel(8)). Also added in /etc/rc0.d and /etc/rd6.d to gracefully
shut down. On Red Hat and variants use the command chkconfig(1) instead.

Be aware that the Linux and Solaris run levels are different. Even some Linux distributions
have different run levels than others. So check your OS documentation first.


How To-Best Practice
Comment List
Related Discussions