Login to your server via SSH
- Run cd [path-to-your-Oxwall-homedir]/ow_cron command to enter the Cron folder
- Run pwd command
- You will see the path to the Cron folder (e. g. /home/yoursite/public_html/ow_cron)
- Run which php command
- You will see the path to PHP (e. g. /usr/local/bin/php)
Put two paths you got into one: path to PHP/path to Cron folder: For example:
/usr/local/bin/php /home/site/public_html/ow_cron/run.phpUse this command in Add New Cron Job section in cPanel.
Note: contact your hosting company if you have troubles with connecting via SSH.
+1100 PID: 8588 (Parent PID:8586)
Account: mine
Uptime: 108 seconds
/home/virtfs/mine/usr/local/bin/phpCommand Line (often faked in exploits):
/usr/local/bin/php /home/mine/public_html/ow_cron/run.php
Network connections by the process (if any):
tcp: 208.67.20.49:56193 -> 195.20.205.9:80
its connect unsecured not ssl port 80
and is use main server ip not dedicated ip
in use curl
208.67.20.50:48866 -> 208.67.20.50:443
is connect ssl port 443
and is use dedicated ip
Account: mine
Resource: Virtual Memory SizeExceeded: 928 > 500 (MB)
Executable: /home/virtfs/mine/usr/local/bin/php
Command Line: /usr/local/bin/php /home/mine/public_html/ow_cron/run.php
PID: 25339 (Parent PID:25338)
Killed: No
now we are back to cron use almost 1 gb ram
Each cron job is executed independent of any other jobs you may have specified. This means that your long-lived script will not impede other jobs from being executed at the specified time.
If any of your scripts are still executing at their next scheduled cron interval, then another, concurrent, instance of your script will be executed.
This can have unforeseen consequences depending on what your script does. I would recommend reading the Wikipedia article on File Locking, specifically the section on Lock files. A lock file is a simple mechanism to signal that a resource — in your case the someScript3.sh script — is currently 'locked' (i.e. in use) and should not be executed again until the lock file is removed.