HLServer: Adding New Keys
From Headus Docs
|
Occasionally you may receive a new or updated license key that needs to be added to a running hlserver process.
[edit] Adding New KeysIf you're simply adding a new key to an existing product, then ...
If the new key is extending the duration of an old key, there is no need to delete the old one; the new key will over-ride the old one. [edit] Adding New ProductsOlder floating license keys look like this ... <- 21 hex numbers -> Product Sysid Expire Ref# Num #v2# 3a d6 ........ a9 42 # uvlayoutv2 690ca1ab never 0920 [001 3] The first word after the # character is the product name for that license. More recent floating licenses look like this ... # hlserver,uvlayoutv2 sysid=690ca1ab expire=071226 [000 4] 8MFP LCDY A0GZ 553N QQ6Z BLMB A1A6 GF1G # 6200 74QX SEPD GEC4 AK1W QJK8 3E5N 2LLF 345C JQX5 24SA # 6201 In this form there will be one or more products listed after hlserver. You will need a PRODUCT line in your hlserver.conf file for each product covered by these license keys. For example, with both the old and new license formats above, this line will need to be added to the hlserver.conf file ... PRODUCT uvlayoutv2 <access_list> More information on the format of the hlserver.conf file can be found in Server Install: Configuration. [edit] Reloading FilesWhenever you make a change to the keys file or hlserver.conf, you'll need to tell hlserver to reload these files. You can do this via the hlmanager "reload" command. More information on hlmanager can be found in The Manager. |