How-to Softlock License Server - Command Line Options
The command line options available differ for each operating system. A brief listing for each platform is given here
.
Windows & macOS
The options for Windows and macOS follow. The most common operations when setting up a server is to first use the -a option to activate the server, then the -i option to install and run the server.
Usage: qps-license-server-x [OPTION]... (1st form) or: qps-license-server -i [OPTION]... (2nd form) or: qps-license-server -u [OPTION]... (3rd form) or: qps-license-server -d [OPTION]... (4th form) or: qps-license-server -a [OPTION]... (5th form) or: qps-license-server -p [OPTION]... (6th form)1st form: runs the floating license from commandline manually.
2nd form: installs the floating license server to be run by the system.
(Windows & Mac OS X only)
3rd form: stops & uninstalls the floating license server from the system.
(Windows & Mac OS X only)
4th form: runs the floating license server as a daemon.
(all non-Windows operating systems)
5th form: activates the floating license server on the computer. This must
be done before the floating license server can be used.
6th form: generates the XML <user /> entry with the bcrypt-hashed password
that can be used in the configuration file to allow access via the
TurboFloat Server manager.
-x Starts the floating license server from
commandline.
-pdets=FILEPATH Specify a custom location to the product
details file (TurboActivate.dat).
-config=FILEPATH Specify a custom location to the config file.
-i Installs this floating license server as a
Windows Service to run when the system boots.
-u Uninstalls this floating license server.
-h Display this help and exit.
-v Output version and activation details then exit.
-a[=PRODUCTKEY] Activates or re-activate this server.
-areq=FILEPATH Generates an "offline activation" request file.
This must be used with the "-a" option.
-aresp=FILEPATH Uses the "offline activation response" file to
activate the floating license server. This
must be used with the "-a" option.
-deact[=FILEPATH] De-activates this server so that it can be
activated on another computer. If you specify
a FILEPATH then an "offline deactivation"
request file is generated.
-p="PASSWORD" Generate an XML <user /> entry with the
bcrypt-hashed password. Must use the -user
switch as well to generate the full XML element.
And you can use the -silent switch to just
output the element and not any of the explanations.
-user="USERNAME" The username that will be output in the XML
<user /> entry.
-wf=WORK_FACTOR The work factor to use when generating the password
hash. If this is not present then an ideal work factor
is chosen (12 or higher depending on the version and
other factors). Choose a work factor between 4 and
31. All numbers outside that range will be ignored in
favor of our default work factor.
-silent Don't output to the screen.
Linux
The command line options for Linux follow. Note that unlike Windows or macOS, there is no -i option. Instead, the option to run the server from the command line, -x, and an option to run as a daemon, -d, are used instead. For testing, it can be convenient to star the server with -x to determine that the server is starting properly. To make managing the server easier, there is a-pidfile option that will write out a lock file to the specified destination. This can help automated scripts to find the correct server to start and stop it. To stop a server, just send SIGTERM to the process.
Again, the usual usage would be to use the -a option to activate a license, then the -x option to verify and test that the server is working initially,then kill the server with Ctrl-C and start itgain with the -d option for operation. Adding the command to /etc/rc.local with the -d and -pidfile options would be recommended. Usually, PID files are written to /var/run, e.g. /var/run/qimera-pro-server.pid for the Qimera Pro server, for example. The file will contain the PID number for that server process. To stop the server, a command such as: e.g.kill `cat var/run/qimera-pro-server.pid` could be used/ An init script could also be written to start and stop the server using the usual init control scripts.
Usage: qps-license-server -x [OPTION]... (1st form) or: qps-license-server -i [OPTION]... (2nd form) or: qps-license-server -u [OPTION]... (3rd form) or: qps-license-server -d [OPTION]... (4th form) or: qps-license-server -a [OPTION]... (5th form) or: qps-license-server -p [OPTION]... (6th form)1st form: runs the floating license from commandline manually.
2nd form: installs the floating license server to be run by the system.
(Windows & Mac OS X only)
3rd form: stops & uninstalls the floating license server from the system.
(Windows & Mac OS X only)
4th form: runs the floating license server as a daemon.
(all non-Windows operating systems)
5th form: activates the floating license server on the computer. This must
be done before the floating license server can be used.
6th form: generates the XML <user /> entry with the bcrypt-hashed password
that can be used in the configuration file to allow access via the
TurboFloat Server manager.
-x Starts the floating license server from
commandline.
-d Starts the floating license server as a daemon.
-pdets=FILEPATH Specify a custom location to the product
details file (TurboActivate.dat).
-config=FILEPATH Specify a custom location to the config file.
-h Display this help and exit.
-v Output version and activation details then exit.
-a[=PRODUCTKEY] Activates or re-activate this server.
-areq=FILEPATH Generates an "offline activation" request file.
This must be used with the "-a" option.
-aresp=FILEPATH Uses the "offline activation response" file to
activate the floating license server. This
must be used with the "-a" option.
-deact[=FILEPATH] De-activates this server so that it can be
activated on another computer. If you specify
a FILEPATH then an "offline deactivation"
request file is generated.
-p="PASSWORD" Generate an XML <user /> entry with the
bcrypt-hashed password. Must use the -user
switch as well to generate the full XML element.
And you can use the -silent switch to just
output the element and not any of the explanations.
-user="USERNAME" The username that will be output in the XML
<user /> entry.
-wf=WORK_FACTOR The work factor to use when generating the password
hash. If this is not present then an ideal work factor
is chosen (12 or higher depending on the version and
other factors). Choose a work factor between 4 and
31. All numbers outside that range will be ignored in
favor of our default work factor.
-silent Don't output to the screen.
-pidfile=FILEPATH Write the process ID to a file