12-18-2006
The man page of crontab is very clear about that:
Quote:
Originally Posted by man page of crontab
If all lines in the crontab file are deleted, the old crontab file is restored. The correct way to delete all lines is to remove the crontab file using the -r option.
If you still want to have the crontab file, you can put in a place holder line that is hashed out and clearly says that it is a place holder, not intended to do anything and should not be modified.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I am trying to schedule a job to run every 15 minutes from 7am to 5:30pm. Could someone show me the syntax for this?
Thanks. (1 Reply)
Discussion started by: bestbuyernc
1 Replies
2. UNIX for Advanced & Expert Users
Sometimes cron really upsets me and I cant figure out these types of wierd dates, but how do I get cron to run something on every other sunday? I am running Solaris 8.
-S (4 Replies)
Discussion started by: Sowser
4 Replies
3. Shell Programming and Scripting
Hi Everyone , have a nice day
given below is the line i have added in crontab
* * * * * /Rauf/script2.sh
intended to run this script after every minute , when i run this script manually it runs fine and produces output , but after adding it to crontab ( like given above ) , it doesnt work
... (5 Replies)
Discussion started by: Dastard
5 Replies
4. AIX
Hi. I'm new to AIX and I need to create a crontab entry to run a script every first 5 business days of the month? please help. (2 Replies)
Discussion started by: udelalv
2 Replies
5. Solaris
How to set the crontab entry for every other Friday?
Regards,
Raj (1 Reply)
Discussion started by: rajip23
1 Replies
6. Solaris
Hi,
i need to setup a cronjob that has will execute iostat command from morning to evening time.
for instance the timing has will be like this.
8:00 A.M -- 6:00P.M
how to define this entry in crontab
Regards (3 Replies)
Discussion started by: jaweedak
3 Replies
7. Solaris
hi
i am new in solaris. i am accessing server through putty. i could not add entry in crontab.
i have given "crontab -e" for add a new entry. It is not coming. what parameter i have to set for getting crontab -e
thanks (1 Reply)
Discussion started by: sunnybee
1 Replies
8. UNIX for Dummies Questions & Answers
Is this the correct entry to touch a file on 6/6 5AM?
00 05 06 06 * touch /support/home/.no_copy Please use next time code tags for your code and data (5 Replies)
Discussion started by: Me XMan
5 Replies
9. Shell Programming and Scripting
Hi all,
I want to remove the remove bracket sign ( ) and put in the separate column I also want to remove the repeated entry like in first row in below input (PA156) is repeated
ESR1 (PA156) leflunomide (PA450192) (PA156) leflunomide (PA450192)
CHST3 (PA26503) docetaxel... (2 Replies)
Discussion started by: manigrover
2 Replies
LEARN ABOUT FREEBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists, then
depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to
use this command. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will
be ignored, and so can be used for comments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/var/cron/allow List of users allowed to use crontab
/var/cron/deny List of users prohibited from using crontab
/var/cron/tabs Directory for personal crontab files
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), cron(8)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'') with the exception that the dangerous variant of calling crontab without a file
name in the first form of the command is not allowed by this implementation. The pseudo-filename '-' must be specified to read from standard
input. The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
May 13, 2010 BSD