08-25-2003
On one machine I helped on, the admin required changes to CRON to be done in the following manner ...
# crontab -l > /dir/cron.chg.YYMMDDHHMM
# edit /dir/cron.chg.YYMMDDHHMM
# crontab /dir/cron.chg.YYMMDDHHMM
Was a bit mundane at first but was a lifesaver if something didn't work as planned - the crontab file was pretty big.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I saw a post on here a while back describing how to edit a crontab file when I'm not able to edit it via crontab -e.
Currently, if I try to do a crontab -e, it just comes back with:
# crontab -e
7987
<and then it just hangs there FOREVER>
If I do a crontab -l, it shows me all of the... (1 Reply)
Discussion started by: FredSmith
1 Replies
2. Shell Programming and Scripting
hi
i need to change crontab settings as
minute,hour,day of month,month year,day of week
certain times. for that i need to go as crontab -e. i want to avoid that as its creating many problems in mysystem.
so here i m planning/trying to write a script that will update the settings in crontab... (8 Replies)
Discussion started by: d_swapneel14
8 Replies
3. UNIX for Dummies Questions & Answers
Hi
I am new to Unix and would like some assistance.
I need to edit the crontab file so that a script is set to run at 3:00 am each day.
When I telnet to the sun server and type crontab -e a black screen appears and I am unable to make any changes.
Could you advice on what is needed to... (11 Replies)
Discussion started by: juliet
11 Replies
4. Solaris
Hi..
At linux
I can edit crontab with command
$crontab -e
BUT I don't know to edit crontab at Solaris
because I tried with command $crontab -e
I can't do that
Can you help me...?
Thanks for solution
regards,
srilinux (25 Replies)
Discussion started by: srilinux
25 Replies
5. Shell Programming and Scripting
Hi All,
There are some cron jobs scheduled already by someone, now I have to make some changes to the schedule timings. Please advise me.
thanks,
Raju (2 Replies)
Discussion started by: rajus19
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I am new to Unix. I have written a script in Unix. I wanted to schedule this script in cronjobs which has to be run daily at 10AM.
Already i have some cron jobs running on my unix server. In addition to these I have to edit the crontab. I know I have to execute the command "crontab -e" to... (9 Replies)
Discussion started by: Sheethal
9 Replies
7. Shell Programming and Scripting
Hi,
Can some one tell me if we can configure the jobs in crontab using a shell script.
I know it can be done easily by using "crontab -e", but i just want to know whether we can add a job into the crontab using a shell script.
If it can be done, plz suggest the procedure to do it.
If it... (6 Replies)
Discussion started by: rudrarajumk
6 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I need to edit the crontab on one of my unix systems. When I execute crontab -e, nothing happens, then I get an error '666' and can't type anything else at the cli.
I tried resizing the window, but still got the same error. I'm using the run user and I've checked the permissions on... (0 Replies)
Discussion started by: bbbngowc
0 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have a solaris 10 box. And I want to schedule a cronjob.But it gives the following error
bash-3.2$ crontab -l
crontab: can't open your crontab file.
bash-3.2$ EDITOR=vi
bash-3.2$ export EDITOR
bash-3.2$ crontab -e
crontab: can't open your crontab file.
I checked in... (12 Replies)
Discussion started by: Rossdba
12 Replies
10. Shell Programming and Scripting
Hi,
I m setting up my crontab for the very first time. I m a non-root user and this is linux
$ export EDITOR=vi
$ crontab -e
no crontab for user1 - using an empty one
crontab: installing new crontab
"/tmp/crontab.uW0JNx":1: bad command
errors in crontab file, can't install.
Do you want... (3 Replies)
Discussion started by: mohtashims
3 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