flo/nsupdate.info
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Releases Activity

update docs about "faults ... --notify-user"

Browse Source
This commit is contained in:
Thomas Waldmann 2014-08-17 01:00:18 +02:00
parent 1f03834463
commit c07188bf71
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/admin.rst
View File

@ -253,7 +253,7 @@ it runs as the same user as the nsupdate.info wsgi application::
# reinitialize the test user: # reinitialize the test user:
50 2 * * * django-admin.py testuser 50 2 * * * django-admin.py testuser
# reset the fault counters: # reset the fault counters:
55 2 * * * django-admin.py faults --flag-abuse=20 --reset-client 55 2 * * * django-admin.py faults --flag-abuse=20 --reset-client --notify-user
# clear expired sessions from the database, use your correct settings module: # clear expired sessions from the database, use your correct settings module:
0 3 * * 1 django-admin.py clearsessions 0 3 * * 1 django-admin.py clearsessions
# clear outdated registrations: # clear outdated registrations:
@ -270,6 +270,10 @@ is over 20 (and, for these cases, it'll also reset the fault counter back to 0).
--reset-client additionally sets all client fault counters back to 0, so all --reset-client additionally sets all client fault counters back to 0, so all
counts are just "per day". counts are just "per day".
--notify-user will send an email notification to the creator of the host if we
set the abuse flag for it. The email will contain instructions for the user
about how to fix the problem.
So, if you run this daily, it means that more than 20 client faults per day are So, if you run this daily, it means that more than 20 client faults per day are
considered abuse (e.g. if someone runs a stupid cronjob to update the IP instead considered abuse (e.g. if someone runs a stupid cronjob to update the IP instead
of a well-behaved update client). of a well-behaved update client).