Disabling Log Rotation service on a single domain
The following request packet disables Log Rotation service on domain example.com:
<packet version="1.5.0.0">
<log-rotation>
<disable>
<filter>
<domain-name>example.com</domain-name>
</filter>
</disable>
</log-rotation>
</packet>
A positive response from the server can look as follows:
<packet version="1.5.0.0">
<log-rotation>
<disable>
<result>
<status>ok</status>
<filter-id>example.com</filter-id>
<id>33</id>
</result>
</disable>
</log-rotation>
</packet>
If the domain was not found, the response from the server looks as follows:
<packet version="1.5.0.0">
<log-rotation>
<disable>
<result>
<status>error</status>
<errcode>1013</errcode>
<errtext>domain does not exist</errtext>
<filter-id>example.com</filter-id>
</result>
</disable>
</log-rotation>
</packet>
Disabling Log Rotation service on multiple domains
The following request packet disables Log Rotation service on domains used by the clients with ID 5 and ID 8:
<packet version="1.5.0.0">
<log-rotation>
<disable>
<filter>
<client-id>5</client-id>
<client-id>8</client-id>
</filter>
</disable>
</log-rotation>
</packet>
If the client with ID 5 was not found on the server and the client with ID 8 runs two domains (ID 17 and 29) the response from the server looks as follows:
<packet version="1.5.0.0">
<disable>
<log-rotation>
<result>
<status>error</status>
<errcode>1015</errcode>
<errtext>client does not exist</errtext>
<filter-id>5</filter-id>
</result>
</disable>
<disable>
<result>
<status>ok</status>
<filter-id>8</filter-id>
<id>17</id>
</result>
</disable>
<disable>
<result>
<status>ok</status>
<filter-id>8</filter-id>
<id>29</id>
</result>
</disable>
</log-rotation>
</packet>