khushabuchand.solan@hcltech.com asked a question.
Steps to Build and Configure a Vendor Daemon on Linux CLI (FlexNet Publisher)
I am working on setting up a vendor daemon for a 64-bit Linux CLI-based environment using FlexNet Publisher. However, most of the documentation I have found (e.g., fnp_devenv.pdf) primarily focuses on GUI-based environments.
I would like to understand the correct approach for a CLI-only setup:
Are there any specific configuration files or scripts required for the Linux setup?
Is there a dedicated guide or documentation available for setting up a vendor daemon in a Linux CLI-based environment?
Any detailed steps, sample commands, or references would be highly appreciated.
Thank you!
Hi @khushabuchand.solan@hcltech.com ,
You can follow the same steps to build the CLI setup.
Hi Y Vernekar,
Thank you for your response. I have already tried following the same steps as in the GUI-based setup, but I am facing an issue in the Linux CLI environment. Here is the error message I am encountering while running this make -f makefile clean all:
"rm -f lm_new.c
./lmnewgen gssl
v8.1+ FlexNet, using TRL
ENCRYPTION_SEEDs or LM_SEEDs in lm_code.h
are non-unique. Set them to 32-bit values
that you make up, and never change them.
And make sure you keep safe copies.
You can use "lmrand1 -seed" to make up numbers if you prefer.
Exiting.
make: *** [makefile:169: lm_new.o] Error 1
"
If you or anyone else has previously worked on setting up a vendor daemon on Linux CLI, could you share step-by-step instructions or any specific configurations that need to be done? A reference to any CLI-specific guide would also be very helpful.
The documentation does have all the steps needed but I will summarise it below:
Hi Y Vernekar,
Thank you for your response. I have successfully built and tested my vendor daemon, and it is working fine. Now, I need to share the necessary steps with my customer so they can use the license without needing to build the vendor daemon themselves.
I plan to provide the following files to the customer:
Vendor Daemon (<vendor> binary for Linux)
License File (.lic)
lmgrd (License Manager Daemon)
Are these the correct steps to share with the customer?
Are there specific sections in the FlexNet Publisher documentation I should refer to for proper deployment guidance?
Thank you in advance!
For just hosting a server on the client end these should be fine.