Hello,
Inside "/etc/cron.d/directadmin_cron" I see:
When issuing both the of the above, they both seem to launch awstats etc. So, is one of these two crontab lines redundant? As it is now, awstats launches in two instances and this obviously consumes system resources.
EDIT:
must be for the monthly bandwidth reset, am I correct? So, it would be a matter to run this cron job on a time where the standard cron job is not running... (Pardon, having the xmas food blues getting to my brain here )
EDIT 2:
Building awstats through the awstats script inside "/usr/local/directadmin/scripts/awstats.sh" made the system get a very high load. Building awstats through custombuild made it operate under normal conditions, not launch several awstats-tasks at once (which was what caused the high load) etc.
An additional inquiry: Would it be possible to run the task.queue processes as "nice"? If so, what would be the correct syntax to do so inside the crontab?
Inside "/etc/cron.d/directadmin_cron" I see:
Code:
* 4 * * * root echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue
20 4 1 * * root echo 'action=reset&value=all' >> /usr/local/directadmin/data/task.queue
When issuing both the of the above, they both seem to launch awstats etc. So, is one of these two crontab lines redundant? As it is now, awstats launches in two instances and this obviously consumes system resources.
EDIT:
Code:
20 4 1 * * root echo 'action=reset&value=all' >> /usr/local/directadmin/data/task.queue
EDIT 2:
Building awstats through the awstats script inside "/usr/local/directadmin/scripts/awstats.sh" made the system get a very high load. Building awstats through custombuild made it operate under normal conditions, not launch several awstats-tasks at once (which was what caused the high load) etc.
An additional inquiry: Would it be possible to run the task.queue processes as "nice"? If so, what would be the correct syntax to do so inside the crontab?
Last edited: