01-14-2015
How can i make my cron/script to generate a log filename with timestamp in it ?
Hello Friends,
I would like my script to display date timestamps in the file name for every script execution.
Below is the scenario: (just for testing purpose)
I scheduled a cron job, lets say it runs every 5 min and record/logs output in to a log file.
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /tmp/test/mytestscpt.sh > /tmp/test/logs/crnlog.log
Here what i wanted to do; instated of over writing or appending the output to an existing log file "crnlog.log"; i would like to create/have separate response/output log file with time stamp in its name.
I tried to make use of "date +%m_%d_%y-%H.%M.%S " ; but was not able to achieve it.
for example;
first run,
it should create
/tmp/test/logs/crnlog.01_14_15-12.00.45.log
after 5 min,
it should run and create
/tmp/test/logs/crnlog.01_14_15-12.05.45.log
another 5 min after that,
It should create
/tmp/test/logs/crnlog.01_14_15-12.10.45.log
And so on.
Could you please give me some idea to implement this?
Thank you.
Last edited by System Admin 77; 01-14-2015 at 01:21 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
whats going on guys. below is a script i made and am just curious if there is a "time stamp" command. so i can set the timestamp in a filename.
#! /bin/ksh
#
# This scripts takes a list of files in the INDIR variable and compairs it to a list of files that are open in the same directory.... (2 Replies)
Discussion started by: Optimus_P
2 Replies
2. Shell Programming and Scripting
Does anyone know how to add a timestamp to a file's name extension in a shell script? Please help.. (3 Replies)
Discussion started by: walterja
3 Replies
3. Shell Programming and Scripting
I've seen several examples of scripts in thise forum about having a script generate a log file. I have a script that is run from cron and that monitors a file system for a specfic filename(s) and then performs some actions on them. Normally I call this script from another script (which the one... (2 Replies)
Discussion started by: heprox
2 Replies
4. Shell Programming and Scripting
Hi
i want to replace the previous time stamp with the current timsatp at the start of the file like
20090710_113354_FT0710a.txt this one to 20091111__113354_FT0710a.txt
thanks in advance (3 Replies)
Discussion started by: Reddy482
3 Replies
5. Shell Programming and Scripting
Good morning. I am searching for "how-to"'s for some particular questions:
1. How to write a script in HP-UX 11.
2. How to schedule a script.
3. How to "call" scripts from the original script.
4. How to su to another user from within a script.
This is the basics of what the... (15 Replies)
Discussion started by: instant000
15 Replies
6. Programming
Hi,
i am trying to create a makefile for my C++ program. when i say "make" it should generate the binary file. and when i say make clean, it should delete all the bins and libs.
can u please help me out. (5 Replies)
Discussion started by: sunshine23
5 Replies
7. Shell Programming and Scripting
Hi.,
My file name is of the format:
name_abc_20100531_142528.txt
where.,
my timestamp is of the format:
yyyymmdd_hhmmss
How to extract the date strring and time string into seperate variables in the shell script, after reading the file as the input?
I want to get the variables... (9 Replies)
Discussion started by: av_vinay
9 Replies
8. Shell Programming and Scripting
Hi,
Below is a directory containing links new2,list,new1.
I need to get the size and timestamp for them.
How do i get these details. Please help
lrwxrwxrwx 1 xxx abc 11 Nov 24 17:34 new2 -> ./org1/new2
lrwxrwxrwx 1 xxx abc 11 Nov 24 17:34 list -> ./org2/list
lrwxrwxrwx 1 xxx abc 10... (2 Replies)
Discussion started by: pradebban
2 Replies
9. Shell Programming and Scripting
Hi Gurus,
I have different files with different timestamp and different base file name, I have to group those files based on basename and provide a unique file name for similar file names.
My Directory has following files.
abc_filename_20130623:00:09:00.txt... (1 Reply)
Discussion started by: user_linux
1 Replies
10. Shell Programming and Scripting
originally the shellscript
#ln_file_name=`echo $ld_interface_date"_"${8}".csv"`
#ln_file_name=`echo 201202011527_HL_HLTM1_B04A.csv`
ln_file_name="*"`echo ${7}".csv"`
get_file_list_1=$log_path"tm1_file_list.gfl1"
cd ${source_path}
echo "Try to find any file exist in the... (10 Replies)
Discussion started by: feilhk
10 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)