Hi Bobbbb,
first of all, you could modify your unique command as:
nice -n 19 ionice -c2 -n7 /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
... to solve the issue, that it didn't seem to have any effect to your CPU/IO usage. Please try as well the full path, if you experience issues, as for example:
/usr/bin/nice -n 19 /usr/bin/ionice -c2 -n7 /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
Please make sure, that "nice" and "ionice" are located at the given paths and don't just copy&paste the suggestion with the whole path - usage ( you could use "locate nice" / "locate ionice" to verify the paths ).
You asked as well for a different execution time, to avoid high usage during office hours. I would recommend to try several spamtrain - cronjobs, which you might setup with
For Plesk 11 you would use:
nice -n 19 ionice -c2 -n7 /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f execute-spamtrain >/dev/null 2>&1
/usr/bin/nice -n 19 /usr/bin/ionice -c2 -n7 /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f execute-spamtrain >/dev/null 2>&1
For Plesk 12 you would use:
nice -n 19 ionice -c2 -n7 /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f ExecuteSpamtrain >/dev/null 2>&1
/usr/bin/nice -n 19 /usr/bin/ionice -c2 -n7 /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f ExecuteSpamtrain >/dev/null 2>&1
or use the direct command with:
nice -n 19 ionice -c2 -n7 /usr/local/psa/admin/sbin/spamtrain >/dev/null 2>&1
/usr/bin/nice -n 19 /usr/bin/ionice -c2 -n7 /usr/local/psa/admin/sbin/spamtrain >/dev/null 2>&1
If you still would like to exclude one of the daily DailyMaintenance - cronjobs from your "50plesk-daily" script, you have to modify the line
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
to all different parts like:
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f Plesk-COMMAND-name1
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f Plesk-COMMAND-name2
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f Plesk-COMMAND-name3
...
... where you have to leave out the commands, which should not be executed daily.
( Please see the current Plesk-commands for the DailyMaintenance - script with "/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -l" and be aware that Plesk 11 and Plesk 12 have different commands! )
From time to time, it is wise to clean up the spamassassin - database ( as you already found out with the linked forum-thread), but I would recommend a 6-month-cronjob and not a monthly one.
Please keep in mind, that spamtraining with spamassassin can be very time investing and you should try out addons, filters and rules to find the most efficient configuration for each, unique server - unfortunately there is no "best-for-all" solution.