10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi,
on AIX
The following
echo "rr" > myfile_$(date +"%m_%d_%Y").log
gives:
myfile_10_23_2019.log
But in crontab:
00 03 * * 1-6 /u01/script.sh >/tmp/myfile_$(date +"%m_%d_%Y").log 2>&1
gives:
myfile_Wed Oct 23 03:00:00 CEST 2019
How can one have:
myfile_10_23_2019.log (6 Replies)
Discussion started by: big123456
6 Replies
2. Shell Programming and Scripting
Hi ,
I have to schedule one job in crontab, but with two parameters.
1. Sysdate in YYYYMMDD format
2. Sysdate - 7 in YYYYMMDD format
Please suggest how to do that.
Thanks in advance. (1 Reply)
Discussion started by: Anupam_Halder
1 Replies
3. Shell Programming and Scripting
Hi,
I'm new to Linux and I'm trying to do some script.
In particular, a part of that script is the following one:
#!/usr/local/bin/bash
path_s="/home/piros2/"
input_list=$path_s"input_list.txt"
date +%Y-%m-%d --date=" 10 days ago" >> $input_list
The script (script.sh) is executed from... (2 Replies)
Discussion started by: Piros
2 Replies
4. Solaris
SOLARIS 9 Zone :
date command in crontab shows delayed(One Hour) output
Hi folks,
the date command shows the correct date and time, How ever, if the date command executed through crontab in any form of scrip the output shows as one hour delayed, similar to date -u..
Can some one help in... (12 Replies)
Discussion started by: judi
12 Replies
5. Solaris
Hi, i wanted to schedule a backup script to run on 7.30pm every 1st Sat of month MAR, APR, SEP, OCT.
Am i understanding it correctly? Because it doesn't seem to run according to the schedule i needed.
= (7.30pm) & (1st to 7th day of the month) & (MAR, APR, SEP, OCT) & (Sat)
30 19 1-7... (1 Reply)
Discussion started by: beginningDBA
1 Replies
6. Solaris
Hi,
0 9 1,2,3,4,5,6,7 3,4 6
I want a cronjob to run on every 1st Sat of Mar & Apr. But the above schedule is running is running on the 1st 7 days. How do i rectify it?
Thanks in advance. (2 Replies)
Discussion started by: beginningDBA
2 Replies
7. Shell Programming and Scripting
Hi Expert,
I am using TZ for extracting yesterday date and day before yesterday date
example :
date_yes=`TZ="GMT+28" date +'%d-%b-%Y'`
date_dbyes=`TZ="GMT+48" date +'%d-%b-%Y'`
echo $date_yes $date_dbyes
26-May-2010 27-May-2010
I have written a small script for the same named... (1 Reply)
Discussion started by: pritish.sas
1 Replies
8. Shell Programming and Scripting
Hello Experts,
I am facing problem in date command with TZ
test.sh
Output : 26-May-2010 27-May-2010
I scheduled this script everyday at 1 a.m
00 01 * * * sh test.sh
when i was called this script test.sh from crontab , it was giving me other output (1 Reply)
Discussion started by: pritish.sas
1 Replies
9. Shell Programming and Scripting
How to check when was the last time the crontab was updated and also what was the modification done ? (2 Replies)
Discussion started by: mail2sant
2 Replies
10. UNIX for Advanced & Expert Users
Hi
I tried to put a cron job which pipes the logfile appended to date +%d
but it didnt work .
anyone know how to make this happen
thanks in advance
-prasad (7 Replies)
Discussion started by: p4cldba
7 Replies
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab 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/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.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.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). If this
option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse
crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake.
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 -l option causes the current crontab to be displayed on standard output. See the note under DEBIAN SPECIFIC below.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 19 April 2010 CRONTAB(1)