HLServer: Adding New Keys
From Headus Docs
Revision as of 01:21, 21 February 2007 (edit) Headus (Talk | contribs) ← Previous diff |
Revision as of 01:53, 21 February 2007 (edit) (undo) Headus (Talk | contribs) Next diff → |
||
Line 1: | Line 1: | ||
- | {{:HLServer: Menu}} Occasionally you may need to add new information to a running hlserver process. | + | {{:HLServer: Menu}} Occasionally you may receive a new or updated license key that needs to be added to a running hlserver process. |
- | == An Entirely New Product == | + | == Adding New Products == |
- | == New Keys for Existing Products == | + | Floating license keys look like this ... |
+ | |||
+ | <- 21 hex numbers -> '''Product''' Sysid Expire Ref# Num | ||
+ | #v2# 3a d6 ........ a9 42 # '''cyeditv4''' 690ca1ab never 0920 [001 3] | ||
+ | |||
+ | The first word after the '''#''' character is the product name for that license, and | ||
+ | you will need a '''PRODUCT''' line in your '''hlserver.conf''' file to match. | ||
+ | |||
+ | PRODUCT '''cyeditv4''' ''<access_list>'' | ||
+ | |||
+ | More information on the format of the '''hlserver.conf''' file can be found in | ||
+ | [[HLServer: Server Install#Configuration|Server Install: Configuration]]. | ||
+ | |||
+ | == Adding New Keys == | ||
+ | |||
+ | If you're simply adding a new key to an existing product, edit the keys file on the server and add the | ||
+ | key string to the end of the file. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | If you want to be sure that the new key is working, but want to leave the old one in there just in case, add a '''#''' character to the beginning of the old key's line; this will temporarily disable it. | ||
+ | |||
+ | == Reloading Files == | ||
+ | |||
+ | Whenever 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 [[HLServer: The Manager|The Manager]]. |
Revision as of 01:53, 21 February 2007
|
Occasionally you may receive a new or updated license key that needs to be added to a running hlserver process.
Adding New ProductsFloating license keys look like this ... <- 21 hex numbers -> Product Sysid Expire Ref# Num #v2# 3a d6 ........ a9 42 # cyeditv4 690ca1ab never 0920 [001 3] The first word after the # character is the product name for that license, and you will need a PRODUCT line in your hlserver.conf file to match. PRODUCT cyeditv4 <access_list> More information on the format of the hlserver.conf file can be found in Server Install: Configuration. Adding New KeysIf you're simply adding a new key to an existing product, edit the keys file on the server and add the key string to the end of the file. 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. If you want to be sure that the new key is working, but want to leave the old one in there just in case, add a # character to the beginning of the old key's line; this will temporarily disable it. 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. |