This document will give the reader an overview of the cron processes that run tasks on an InterWorx-CP server. It will explain what they are, why they are important, and what the repercussions would be if they were disabled or deleted.
WARNING: Do not edit the iworx or system cron unless you know exactly what you are doing and are well versed in both InterWorx and Linux.. This document will attempt to explain what the repercussions of doing so could be, but as always with something this complex it is possible that other unforeseen things might happen resulting in a malfunctioning server and lost data. If you choose to edit anything always remember to make backups. This is presented here for informational purposes only and is NOT supported.
If you need to know if a particular cron process is running, the cron error log is located /var/log/cron. Run tail -10 /var/log/cron to view the last 10 entries.
The Cron processes above, run by the iworx user are the ones that most InterWorx sysadmins will be interested in, however there are other system cron processes (generally run by root) which support InterWorx, and deserve a mention.
InterWorx Cron Documentation
Purpose:
This document will give the reader an overview of the cron processes that run tasks on an InterWorx-CP server. It will explain what they are, why they are important, and what the repercussions would be if they were disabled or deleted.
Audience:
Advanced System Administrators.
iworxor system cron unless you know exactly what you are doing and are well versed in both InterWorx and Linux.. This document will attempt to explain what the repercussions of doing so could be, but as always with something this complex it is possible that other unforeseen things might happen resulting in a malfunctioning server and lost data. If you choose to edit anything always remember to make backups. This is presented here for informational purposes only and is NOT supported.Overview:
The following cron process are run by the iworx system user and should not be deleted or edited unless there is a specific reason to do so.
Configuring Cron in the iworx.ini file
In the file
/home/interworx/iworx.iniCron Error Log
If you need to know if a particular cron process is running, the cron error log is located
/var/log/cron. Runtail -10 /var/log/cronto view the last 10 entries.InterWorx CRON Processes
The InterWorx cron file is encrypted, however here is a summary of each process run by the
iworxuser and what it does.cron fively (runs every five minutes)
fively - rrd graphs updated, dns exported, and if in the iworx.ini has runtime=fively (the default) it does bandwidth and storage calculations too
cron fifteenly (runs every fifteen minutes)
fifteenly - bandwidth and storage if runtime=fifteenly
cron hourly (runs every hour)
hourly - bandwidth and storage if runtime=hourly
cron quad_daily (runs every day -- every six hours)
quad_daily - license.sync, and bandwidth and storage if runtime=quad_daily
cron daily (run every 24 hours)
daily - OS update, bayes training, and bandwidth and storage if runtime=daily
Specifically:
cron weekly (runs every 7 days)
does not do anything at the moment.
cron monthly (runs every month}
does not do anything at the moment.
System Cron Processes
The Cron processes above, run by the
iworxuser are the ones that most InterWorx sysadmins will be interested in, however there are other system cron processes (generally run byroot) which support InterWorx, and deserve a mention.cron fively (runs every five minutes)
cron fifteenly (runs every fifteen minutes)
cron hourly (runs every hour)
cron quad_daily (runs every day -- every six hours)
cron weekly (runs every 7 days)
cron monthly (runs every month}
How To: