vlmcsd-svn1099-2016-10-25-Hotbird64

This commit is contained in:
Wind4
2016-10-31 20:59:15 +08:00
parent 936811ff5c
commit fcbbc40d60
39 changed files with 904 additions and 305 deletions

View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
@ -386,12 +386,60 @@ to TRUE on a system with no reliable time source,
activations will fail. It is ok to set the correct system
time after you started <b>vlmcsd</b>(8).</p>
<p style="margin-left:11%;"><b>MaintainClients</b></p>
<p style="margin-left:22%;">Can be TRUE or FALSE (the
default). Disables (FALSE) or enables (TRUE) maintaining a
list of client machine IDs (CMIDs). TRUE is useful to
prevent emulator detection. By maintaing a CMID list,
<b>vlmcsd</b>(8) reports current active clients exactly like
a genuine KMS emulator. This includes bug compatibility to
the extent that you can permanently kill a genuine KMS
emulator by sending an &quot;overcharge request&quot; with a
required client count of 376 or more and then request
activation for 671 clients. <b>vlmcsd</b>(8) can be reset
from this condition by restarting it. If FALSE is used,
<b>vlmcsd</b>(8) reports current active clients as good as
possible. If no client sends an &quot;overcharge
request&quot;, it is not possible to detect <b>vlmcsd</b>(8)
as an emulator with
<b>MaintainClients&nbsp;</b>=&nbsp;FALSE. Maintaining
clients requires the allocation of a buffer that is about 50
kB in size. On hardware with few memory resources use it
only if you really need it.</p>
<p style="margin-left:22%; margin-top: 1em">If you start
<b>vlmcsd</b>(8) from an internet superserver, this setting
cannot be used. Since <b>vlmcsd</b>(8) exits after each
activation, it cannot maintain any state in memory.</p>
<p style="margin-left:11%;"><b>StartEmpty</b></p>
<p style="margin-left:22%;">This setting is ignored if you
do not also specify <b>MaintainClients&nbsp;</b>=&nbsp;TRUE.
If you specify FALSE (the default), <b>vlmcsd</b>(8) starts
up as a fully &quot;charged&quot; KMS server. Clients
activate immediately. <b>StartEmpty&nbsp;</b>=&nbsp;TRUE
lets you start up <b>vlmcsd</b>(8) with an empty CMID list.
Activation will start when the required minimum clients (25
for Windows Client OSses, 5 for Windows Server OSses and
Office) have registered with the KMS server. As long as the
minimum client count has not been reached, clients end up in
HRESULT 0xC004F038 &quot;The count reported by your Key
Management Service (KMS) is insufficient. Please contact
your system administrator&quot;. You may use <b>vlmcs</b>(1)
or another KMS client emulator to &quot;charge&quot;
<b>vlmcsd</b>(8). Setting this parameter to TRUE does not
improve emulator detection prevention. It&rsquo;s primary
purpose is to help developers of KMS clients to test
&quot;charging&quot; a KMS server.</p>
<p style="margin-left:11%;"><b>ActivationInterval</b></p>
<p style="margin-left:22%;">This is the same as specifying
<b>-A</b> on the command line. See <b>vlmcsd</b>(8) for
details. The default is 2 hours. Example: ActivationInterval
= 1h</p>
details. The default is 2 hours. Example:
ActivationInterval&nbsp;=&nbsp;1h</p>
<p style="margin-left:11%;"><b>RenewalInterval</b></p>