vovserver Licensing

When using RLM, the behavior of vovserver is controlled by different features depending on the product:

Product NickName Features
Monitor-basic lms server_lms (optional)
Monitor lm One token of server_lm plus multiple tokens of user_licmon
Accelerator nc server_nc, plus tokens of slots_nc

The number of NC slots_nc license tokens consumed by an NC tasker is the lesser of the number of configured NC job slots and the number of logical CPUs on the host.

FlowTracer ft server_ft plus tokens of slots_ft
Allocator la server_la plus tokens of users_la
Accelerator Plus wx server_wx plus tokens of slots_wx

slots_wx tokens consumed by an Accelerator Plus queue nstance = (number of WX taskers in the base queue) + (number of logical CPUs on the Linux host where the Accelerator Plus server is running

To find out the product supported by a vovserver, use:
> source /<install_path>/<version>/<platform>/common/etc/vovrc.csh
% vovsh -x 'vtk_generic_get project info; puts $info(product)'
To change the value of RLM_LICENSE used by a vovserver, use:
> source /<install_path>/<version>/<platform>/common/etc/vovrc.csh
% vovsh -x 'vtk_server_setenv RLM_LICENSE 7070@newhost'

If vovserver loses a feature, it will keep running for a grace period of five days.

If the vovserver fails to get the appropriate license upon startup, or if the grace period expires, it will go into "License Violation", which essentially means that dispatching to remote taskers is disabled. Every other behavior remains fully functional.

To check the current licensing status, visit /cgi/license.cgi.