09-08-2009
Quote:
Well, to know about cron and crontab, you can simple search this forum or use Google and search the net.
Cron is basically a chronograph that executes an executable file at a specific time or times.
Crontab is the table (file) that holds instructions for Cron.
Regarding cPanel, you will not find much help on
cPanel here. Most people here are UNIX/Linux jockeys who prefer not to use cPanel, and instead they manage their processes from the command line (shell).
That is why I gave you a link (below) to a tutorial on this. I think if you do a bit of homework (search and read) and then review the tutorial, you will be good to go. You can post back if you have specific issues/questions after you do some background reading.
Thanks Neo! I have done my homework as you said, Its a diffent ball game with cPanel, all i entered was the path to my file,
Its seems to be working now! but i got this message
Permission denied
what can i do?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Gurus
I need to add a new cronjob to a list. There are already 7-8 cronjobs when I do crontab -e. I need to add a new cronjob without disturbing the existing ones. Can you please tell me how to do that. I am not so good in vi editor as well, but I can do it with some guidance. this is urgent,... (3 Replies)
Discussion started by: ragha81
3 Replies
2. UNIX for Dummies Questions & Answers
can anybody explain the usage of CRON for adding a cron job. please provide an example also for better understanding !!!
Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies
3. Solaris
hi,
how i woulsd be able to find that my cron job is running or not..
E.g abc (2 Replies)
Discussion started by: sam.whocares
2 Replies
4. Solaris
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies
5. Shell Programming and Scripting
Hi all,
Pretty new to CRON but have been messing with Ubuntu for a while now
Here is the situation/problem I have run into you.
I currently run a very basic back procedure by executing a daily CRON job which copies all data from one directory to a USB drive & date stamps the copy:-
cp... (2 Replies)
Discussion started by: 2scoops
2 Replies
6. Shell Programming and Scripting
Hi,
Can anyone help me in finding how to run a specific job every hour without using crontab.
Say for example i need to run a command ps -aux in the starting of every hour.. (3 Replies)
Discussion started by: glv
3 Replies
7. Solaris
Hi ,
I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility )
I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies
8. Shell Programming and Scripting
Hi,
Someone please help me to run the script to maintain a Job: Which can be run for every one hour and should maintain the last two hours files only. It should delete the rest of the files in a dir.
Please suggest me with the sample script.
Thanks !!
Reagrds,
Rama (5 Replies)
Discussion started by: ramagore85
5 Replies
9. Shell Programming and Scripting
Hi
I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies
10. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable
in the crontab, if such exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO
crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)
AUTHORS
Paul Vixie <paul@vix.com>
BSD
June 17, 2007 BSD