7x31/py-kms
1
0
Fork 0
mirror of https://github.com/SystemRage/py-kms.git synced 2025-09-29 00:49:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

preliminar logfile loglevel corrections

Matteo ℱan
2019-05-16 00:30:55 +02:00
parent 3ffeaa790b
commit cba0b35e47
1 changed files with 18 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
Manual.md

@@ -489,35 +489,35 @@ Follows a list of usable parameters:
-s or --sqlite
Use this option to store request information from unique clients in an SQLite database.
-v or --loglevel <{CRITICAL, ERROR, WARNING, INFO, DEBUG}>
-V or --loglevel <{CRITICAL, ERROR, WARNING, INFO, DEBUG}>
Activate verbose logging. Use this flag to set a loglevel. The default is ERROR.
( example: user@user ~/path/to/folder/py-kms $ python server.py -v INFO
produces in "pykms_server.log" these initial messages:
Mon, 12 Jun 2017 22:09:00 INFO TCP server listening at 0.0.0.0 on port 1688.
Mon, 12 Jun 2017 22:09:00 INFO HWID: 364F463A8863D35F )
( example: user@user ~/path/to/folder/py-kms $ python pykms_Server.py -V INFO
produces in "pykms_logserver.log" these initial messages:
Mon, 12 Jun 2017 22:09:00 INFO TCP server listening at 0.0.0.0 on port 1688.
Mon, 12 Jun 2017 22:09:00 INFO HWID: 364F463A8863D35F )
-f of --logfile <LOGFILE>
Create a "LOGFILE.log" logging file. The default is named "pykms_server.log"
-F of --logfile <LOGFILE>
Create a "LOGFILE.log" logging file. The default is named "pykms_logserver.log"
( example: user@user ~/path/to/folder/py-kms $ python server.py 192.168.1.102 8080 -f ~/path/to/folder
/py-kms/newfile.log -v INFO -w random
( example: user@user ~/path/to/folder/py-kms $ python pykms_Server.py 192.168.1.102 8080
-F ~/path/to/folder/py-kms/newfile.log -V INFO -w random
produces in "newfile.log" these initial messages:
Mon, 12 Jun 2017 22:09:00 INFO TCP server listening at 192.168.1.102 on port 8080.
Mon, 12 Jun 2017 22:09:00 INFO HWID: 58C4F4E53AE14224 )
#### _client.py Options_.
***
If something does not work, it may have the cause that _py-kms_ server does not work correctly. You can test this with the KMS client _client.py_, running on the same machine where you started _server.py_.
If something does not work, it may have the cause that _py-kms_ server does not work correctly. You can test this with the KMS client _pykms_Client.py_, running on the same machine where you started _pykms_Server.py_.
For example ( in separated bash windows ) run these commands:
```
user@user ~/path/to/folder/py-kms $ python server.py -v DEBUG
user@user ~/path/to/folder/py-kms $ python client.py 0.0.0.0 1688 -v DEBUG
user@user ~/path/to/folder/py-kms $ python pykms_Server.py -V DEBUG
user@user ~/path/to/folder/py-kms $ python pykms_Client.py 0.0.0.0 1688 -V DEBUG
```
or if you want better specify:
```
user@user ~/path/to/folder/py-kms $ python server.py YOUR_IPADDRESS 1688 -v DEBUG
user@user ~/path/to/folder/py-kms $ python client.py YOUR_IPADDRESS 1688 -v DEBUG
user@user ~/path/to/folder/py-kms $ python pykms_Server.py YOUR_IPADDRESS 1688 -V DEBUG
user@user ~/path/to/folder/py-kms $ python pykms_Client.py YOUR_IPADDRESS 1688 -V DEBUG
```
You can also put further parameters as defined below:
@@ -548,11 +548,11 @@ You can also put further parameters as defined below:
Use this flag to manually specify an ASCII MACHINENAME to use. If no MACHINENAME is specified
a random one will be generated.
-v or --loglevel <{CRITICAL, ERROR, WARNING, INFO, DEBUG}>
-V or --loglevel <{CRITICAL, ERROR, WARNING, INFO, DEBUG}>
Activate verbose logging. Use this flag to set a loglevel. The default is ERROR.
-f of --logfile <LOGFILE>
Create a "LOGFILE.log" logging file. The default is named "pykms_client.log".
-F of --logfile <LOGFILE>
Create a "LOGFILE.log" logging file. The default is named "pykms_logclient.log".
## Activation Procedure
Briefly the product asks for a key during installation, so it needs to enter the GVLK. Then user can set connection parameters, while KMS server must already be running on server machine. Finally with specific commands activation occurs automatically and can be extended later every time for another 180 ( or 45 ) days.
@@ -571,7 +571,7 @@ Briefly the product asks for a key during installation, so it needs to enter the
2. Then put your product's GVLK.
3. Set connection parameters.
4. Try online activation, but... if that fails with error ```0xC004F074``` you’ll most likely have to configure your firewall that it accepts incoming connections on TCP port 1688.
So for Linux users ( server-side with server.py running ): ```sudo ufw allow 1688``` ( to remove this rule ```sudo ufw delete allow 1688``` )
So for Linux users ( server-side with pykms_Server.py running ): ```sudo ufw allow 1688``` ( to remove this rule ```sudo ufw delete allow 1688``` )
5. Attempt online activation ( with now traffic on 1688 enabled ).
6. View license informations ( facoltative ).