08-31-2010
In addition to the type of quotes, the "%" character is special to cron (it means "newline"). All the "%" characters need quoting as "\%".
You will be better putting long commands into a script file and executing that from cron. This also gives you somewhere to set the environment for your commands.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I am not able to edit crontab.
Following is the comand that is being issued
$crontab -e
2764 ............ This is what I am able to see
But when I do
$crontab -l
List of all the crontab entry is displayed.
Also I am seeing one entry in my /etc/cron.d
prw------- 1 root ... (6 Replies)
Discussion started by: pankajkrmishra
6 Replies
2. Shell Programming and Scripting
I have 2 files:-
file1 and file2
file1
SEED
RPTT
TST8
file2
SEED:db1:Y
RPTT:db2:Y
SED8:db2:N
TST8:db:Y
TRN8:db:N
CNV8:db:Y
TEST:db:Y
I have to change third field of file2 to "y" for every entry in file1 matches first filed of file 2
and rest to N (2 Replies)
Discussion started by: okreporthai
2 Replies
3. Solaris
Hi
since we migrated from Solaris 8 to Solaris 10 I do miss a nice feature when editing crontab with vim editor: no more color highlighting after starting to edit. Well there is a hack, see below.
I did define:
export EDITOR='vim -c ":source /export/home/duc904/.vimrc"'
Under Sol8 when... (2 Replies)
Discussion started by: duc904
2 Replies
4. UNIX for Dummies Questions & Answers
I want to set up a file with crontab to run the cron deamon so I can use at to schedule jobs. I think the crontab file (or whatever you call it) has to be set up. Currently, I don't have a crontab file (I checked by typing sudo crontab -u myusername -l), and I don't know the syntax for creating... (6 Replies)
Discussion started by: Ultrix
6 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
Ref: "build crontab from a text file" in same forum. (I am not allowed to post URL's in the first post)
We are reorganizing our UNIX Crontab file by first making changes in a word pad text file. The intent is to then copy it back to Crontab. Will this work? Copy and Paste does not... (6 Replies)
Discussion started by: nivedhitha
6 Replies
6. Shell Programming and Scripting
Hi all,
I am trying the following
I am hoping that the crontab would be changed.
but it prints the previous crontab and says
Can anyone tell me the correct ksh command that should be used here?
I don't want to edit the crontab with crontab -e, I need to edit it via ksh.
Thank... (2 Replies)
Discussion started by: ajaba
2 Replies
7. Shell Programming and Scripting
I have a file which has 10 million records in it. When am trying to edit the file with vi, the following error occurs:
~
~
~
~
~
~
~
~
"file1" Value too large for defined data type
Is there any way that I can edit this file without using vi? Any help would be really appreciated.... (8 Replies)
Discussion started by: bobby1015
8 Replies
8. Shell Programming and Scripting
Hi Geeks
I am working on trimming the logs and extracting the XMLs from it. I am facing one problem here.
My XML String is ending with
...........Request></Body></Envelope>S/R
sometimes there is more then just S/R in the end.
I want to delete anything comes after </Envelope>... (3 Replies)
Discussion started by: santy00110011
3 Replies
9. Solaris
Hi,
OS - SunOS
I gave crontab -e then it returns zero.
$ crontab -e
0
?
?
Crontab status -
$ ps -ef | grep cron
root 2481 1 0 May 12 ? 0:18 /usr/sbin/cron
Please help (9 Replies)
Discussion started by: nag_sathi
9 Replies
10. Shell Programming and Scripting
Dear Guru's
I'm using Putty and want to edit a file. I know we generally use vi editor to do it. As I'm not good in using vi editor, I want to convert the vi into something like text pad. Is there any option in Putty to do the same ? Thanks for your response.
Srini (6 Replies)
Discussion started by: thummi9090
6 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron 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).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD