38,897
edits
(Importing a new version from external source) |
(Importing a new version from external source) |
||
Line 1: | Line 1: | ||
== Configuring your license file == | == Configuring your license file == | ||
Our module for LS-DYNA is designed to look for license information in a few places | Our module for LS-DYNA is designed to look for license information in a few places, one of which is your home folder. If you have your own license server, you can write the information to access it in the following format: | ||
{{File | {{File | ||
|name=ls-dyna.lic | |name=ls-dyna.lic | ||
Line 7: | Line 7: | ||
#LICENSE_TYPE: network | #LICENSE_TYPE: network | ||
#LICENSE_SERVER:<port>@<server> | #LICENSE_SERVER:<port>@<server> | ||
}}and put this file in the folder <tt>$HOME/.licenses/</tt> on each cluster where you plan to submit | }}and put this file in the folder <tt>$HOME/.licenses/</tt> on each cluster where you plan to submit LS-DYNA jobs. Note that firewall changes will need to be done on both our side and yours. To arrange this, send an email containing the service port and IP address of your floating license server to [[Technical support]]. To check if your new license file is responding run the following commands: | ||
<code>module load ls-dyna | <code>module load ls-dyna | ||
ls-dyna_s</code> | ls-dyna_s</code> | ||
The output should contain defined (non-empty) values for <code>Licensed to:</code> and <code>Issued by:</code>, press ^c to exit. | The output should contain defined (non-empty) values for <code>Licensed to:</code> and <code>Issued by:</code>, press ^c to exit. |