Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 20-Dec-2021 | - | ||||
automc/ | H | 03-May-2022 | - | 2,652 | 1,953 | |
README.nightly | H A D | 20-Dec-2021 | 1.6 KiB | 42 | 30 | |
corpus-cleanup | H A D | 20-Dec-2021 | 4.5 KiB | 179 | 135 | |
corpus-hourly | H A D | 20-Dec-2021 | 13.5 KiB | 524 | 416 | |
corpus-nightly | H A D | 20-Dec-2021 | 2.3 KiB | 100 | 60 | |
corpus-nightly.post-svn | H A D | 20-Dec-2021 | 2.3 KiB | 115 | 66 | |
corpus-tagtime | H A D | 20-Dec-2021 | 419 | 18 | 9 | |
corpus.example | H A D | 20-Dec-2021 | 1.4 KiB | 50 | 34 | |
get-rulemetadata-for-revision | H A D | 20-Dec-2021 | 2.9 KiB | 137 | 95 | |
import-logs | H A D | 20-Dec-2021 | 3.7 KiB | 158 | 113 | |
list-bad-rules | H A D | 20-Dec-2021 | 9.3 KiB | 333 | 211 | |
markup-rules-file-with-freqs | H A D | 20-Dec-2021 | 694 | 40 | 28 | |
nightly-slave-start | H A D | 20-Dec-2021 | 1.7 KiB | 62 | 36 | |
nightly-slave-stop | H A D | 20-Dec-2021 | 685 | 33 | 21 | |
nightly-slaves-start | H A D | 20-Dec-2021 | 73 | 7 | 3 | |
nightly-slaves-stop | H A D | 20-Dec-2021 | 72 | 7 | 3 | |
reports-from-logs | H A D | 20-Dec-2021 | 19.4 KiB | 708 | 506 | |
rule-hits-over-time | H A D | 20-Dec-2021 | 12.7 KiB | 530 | 391 |
README.nightly
1Maintainer for this stuff: Daniel Quinlan 2(rather obvious hint, isn't it?) 3 4Scripts to handle running nightly mass-checks and merging results. 5 6Recommended stuff: 7 8 - account to run the nightly/hourly jobs 9 10 - various directories: 11 12 $HOME/scripts - the scripts 13 $HOME/log - cron job logs 14 $HOME/tmp - temporary files and "tagtime" timestamp file 15 $HOME/cvs/spamassassin - the tree (checked out with the correct tag) 16 $HOME/cvs/spamassassin/corpus - the corpus description (for "mass-check -f") 17 18 - $HOME/.corpus contains various settings, see corpus.example in this 19 directory. 20 21 - A cron job (hours for tagtime and corpus-nightly for your 22 local time, this is US/Pacific, adjust appropriately for your 23 timezone) 24 25 The "tagtime" and "corpus-nightly" cron jobs will automatically handle 26 daylight savings, since cron does not. They do this by sleeping for 1 hour 27 if they detect that they are run in the 0800-0859 hour. (This means you can 28 "corpus-nightly" any other time of day, if you want). 29 30 The "corpus-hourly" script only needs to be run if you are producing 31 optional mass-check summary reports. 32 33 "pyzor discover" only needs to be run if you are running Pyzor. 34 35------- start of cut text -------------- 36PATH=/home/corpus/scripts:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin 370 1 * * * corpus-tagtime 3810 1 * * * corpus-nightly >/home/corpus/log/nightly 2>&1 3930 * * * * corpus-hourly >/home/corpus/log/hourly 2>&1 405 1 * * * pyzor discover >/dev/null 2>/dev/null 41------- end ---------------------------- 42