04-13-2009
Hi
Suppose that the code is written in the file a.sh.
Now the crontab has a entry
* * * * * /dit/scheduler/bcp/a.sh
Every minute it checks whether a.sh is running or not.
Now suppose that the the wrapper started today.The log file name will be
130409.log1.Now i want that the next day i.e tomorrow the log file should be generated with the name 140409.log1.
Thanks & regards
Ankit Goel
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I hope this is problem makes sense and that someone can offer some advice.
Basically i have a perl script which accesses a database and outputs the information to a file.
Is it possible to use a 'system' command to embeb some Unix command which moves that file to another directory... (3 Replies)
Discussion started by: Stormrider
3 Replies
2. Shell Programming and Scripting
Is it possible to run <talk> such that both sides of the conversation are written to the screen and also to a file?
I use the utility to chat with collaborators and sometimes it would be nice to have a record of our conversation while we are problem solving.
I am running OS X, so <talk>... (4 Replies)
Discussion started by: cej
4 Replies
3. Shell Programming and Scripting
Hi. I'm a newbie in scripting and i have this problem: i want to use the 'fuser' command on a file to tell if it's being accessed (for my purposes: still being written). I want to save the output of the command and later compare with the 'not being used' result.
the script:
#!/bin/bash... (2 Replies)
Discussion started by: nunovc
2 Replies
4. Shell Programming and Scripting
I have a Bourne Shell script that is normally run as a background job and redirects it's output to a file internally (using exec >>); I use "set -x" to capture each command which provides me with a nice shell execution log if it all goes to pieces.
I now also need to be able to also run this as... (4 Replies)
Discussion started by: AncientCoder
4 Replies
5. Shell Programming and Scripting
Hi All,
Is there a way in Bash we can redirection some output to both console and the file at the same time.
~Parag (2 Replies)
Discussion started by: paragkalra
2 Replies
6. Shell Programming and Scripting
Hi,
Below is the whole string which is to be redirected to the new file.
su - oracle -c "exp $user/$pass file=/oracle/oradata/backup/exp_trn_tables_`date +%d_%b_20%y_%H_%M_%S`.dmp log=/oracle/oradata/backup/exp_trn_tables_`date +%d_%b_20%y_%H_%M_%S`.log tables=table1,table2 statistics=none"
... (3 Replies)
Discussion started by: milink
3 Replies
7. Shell Programming and Scripting
Hello All,
I have some unique requirement.
I have written a very lengthy script which calls number of resource script to execute a particular task.
What I want is output of each command(called from main script and resource scripts) should go to a... (3 Replies)
Discussion started by: anand.shah
3 Replies
8. Linux
When i am issuing chage command, it reporting the output properly.
But when i redirect the output, i am not getting the output in the mentioned path.
chage -l root >> /tmp/chage.txt.
I need to use this into the script to capture the data. I think its seems to be bug with RHEL 6.3. Same... (3 Replies)
Discussion started by: Srini.rk1983
3 Replies
9. Programming
Hi,
I have to redirect output of the command "perldoc perllocal" to new file which
contains all the perl module installed.
Currently using
perldoc perllocal >> mod_data
This does not contain all perl modules installed locally on machine, and each character is doubled.
Please... (3 Replies)
Discussion started by: asak
3 Replies
10. Shell Programming and Scripting
Hi,
I have created script which redirect the output to file.I am able to get the output in file but not in the format.
Output :Content of the log which have 10 -15 lines.
Actal :Line1 ..Line 2Line3 Line4 Line 5
Expected:Line1
Line 2
Line3
Please... (7 Replies)
Discussion started by: karthik771
7 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