On Solaris 10 server the system date won't match with the timestamp on files created by a cron jobs, Please help
here is what i get when i check for system date
at same time i executed a cron job, and checked time stamp on log generated from cron Job
Don't know what's causing this issue
so the system date is "Tue Apr 24 15:27:43" and time stamp on the file created by cron is "Apr 24 10:10"
Hi All,
I am working on a korn shell script.
i have a file such as:
DS.PETSCO.20060601203514.20060531.ctl_20060717124431
i have 2 problems here.
1) i have to capture the time stamp from
the above file i.e this number 20060717124431.
format of time stamp is YYYYMMDDHHMMSS.
can... (4 Replies)
Hi all,
I want to grep a file name with time stamp as 30 minutes how can i??.
Ex
I will getting outputs in a file every minutes
I want to grep it by a time intervals of 30 and show it . Any help will be great !
Thanks,
Arun. (1 Reply)
I have a requirement of checking the current system time and performing certain actions in a shell script. example:
if the current system time is greater than 1400 hrs, then perform step 1,2,3
if the current system time is greater than 1000 hrs, then perform step 1,2
if the current system time... (2 Replies)
i am using function
gethrtime() in sun solaries
to get the time independent of the system time.Problem with this function is if we restart the system time will change to '0'.is there any other way to resolve this problem.
thanks & regards
suresh (3 Replies)
Hi,
I have to find the next time stamp in perl.
Here is the code.
@time = loaltime(time);
print "\n Present time: $time:$time:$time \n";
For example if the time is: "12:55:02" after some process the time becomes 1:00:00.
How do i check when it becomes 00:00 i.e from "12:55:02... (0 Replies)
hi everyone
i am facing a strange problem here
suppose content of my file is
a=1,2,3
b=2,3,4
c=4,5,6
time=
now the problem is i want to add value in front of time variable
and the value should be i format only "HHMMSS"
so it should be like this
a=1,2,3
b=2,3,4
c=4,5,6... (3 Replies)
Here is two time I have:
Jul 12 16:02:01
Jul 13 01:02:01
and how can I do a simple match to get difference between two time which is 09:00:00
Thanks in advance. (3 Replies)
Hi All,
I am facing small problem.
i want to print file time stamp on which date file has placed in the server.
i have given some code but its not giving the year.
any help appreciated.
regards
rajesh. (4 Replies)
I have a log file which wrote time stamp like this
2013-02-11 00:46:40.389037
2013-02-12 11:46:40.197045
can any one help me to get the time stamp difference of these two line in seconds. (4 Replies)
Hi All
i have a file data like below format
A, B
2016-04-14 16:30:00,2016-04-14 16:31:17
2016-04-14 16:40:00,2016-04-14 16:41:10
2016-04-14 16:50:00,2016-04-14 16:50:41
2016-04-14 17:00:00,2016-04-14 17:00:35
2016-04-14 17:10:00,2016-04-14 17:11:48
2016-04-14 17:20:00,2016-04-14 17:20:37
i... (2 Replies)
Discussion started by: Tarak_nath
2 Replies
LEARN ABOUT NETBSD
cron
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