How does lmgrd -local option impact lmremove command
Can a user execute the lmremove command to release an orphaned license if the lmgrd was started with the -local option? Keep in mind the user does not have access to the linux machine on which the lmgrd was started. Below is the command that was used to start the lmgrd on a different linux machine.
lmgrd -local -c <license_file> -log <log_file>
I am looking for a way users can release orphaned licenses and so far it seems lmremove would be the solution that least impacts other users. However, since the lmgrd was started with the -local option to prevent them from running the lmdown command, I wonder if this will also prevent them from running the lmremove command. As mentioned earlier, the user does not have access to the linux machine on which the lmgrd was started.
On UNIX systems, -local restricts the lmdown and lmreread commands to be run only from the same system where lmgrd is running. On Windows systems, if -local is used on its own, lmutil (and variations) can be run by any Local User as long as they are running lmutil from the same host as the license server. If lmgrd is started with -2 -p -local, lmgrd and the vendor daemon can only interact with the command-line utilities (lmreread, lmnewlog, lmdown, lmremove, and lmswitch) if these are located on the same machine and if they are run with LOCALSYSTEM privileges. All platforms: In the case of a three-server setup, any node in the triad is considered to be local. So in your case running lmremove from a different machine should not be a problem.
