11-30-2009
*/1 means every minute.
* means every minute...
*/n means every n'th minute... if n = 1, then */n = *
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I have a shell script which works fine at the command line
and does works in crontab also but does not send the output to
mail as other scripts do by default.
10 1 * * * /export/home/test/report_script
by default should send the output to mail but the script
runs OK and the output... (1 Reply)
Discussion started by: run_time_error
1 Replies
2. UNIX for Dummies Questions & Answers
dear all ,
does any one now how can i become sure that the crontab that i put was working successfully not by looking for thr result of the sheduled task but from a log for the crontab or something similar
and i need to check that the cron i wrote is correct
00 15 * * 0,1,2,3,6... (2 Replies)
Discussion started by: habuzahra
2 Replies
3. UNIX for Dummies Questions & Answers
How can I run "crontab" (parameters) every 6 hours on solaris machine?
Thanks (1 Reply)
Discussion started by: gen4ik
1 Replies
4. Shell Programming and Scripting
i have a ksh script that creates messages in a temp directory and then sends them out using the sendmail command and i'm trying to set it up to run every night with crontab.
So the basic gist of the script is
#create temp dir and messages
...
#loop through each message and send using sendmail... (3 Replies)
Discussion started by: bob122480
3 Replies
5. UNIX for Dummies Questions & Answers
hi all
how to schedule the crontab file in unix? (2 Replies)
Discussion started by: ss4u
2 Replies
6. Shell Programming and Scripting
Hi All,
I've a shell script which calls a Sybase stored procedure to do some functionality. I want to schedule the running of this script by crontab. I'm using Solaris 5.8. When i executed the following command
crontab -l
i got the output as
crontab: can't open your crontab file
How... (10 Replies)
Discussion started by: sumesh.abraham
10 Replies
7. UNIX for Advanced & Expert Users
hi,
I run a .sh file using crontab. I need to know the path of the file . Previously when I run the file alone , i used "pwd" but now when using crontab it gives the temp directory of the file.
Is there any way I can find the absolute path of the file when i execute it ?
Regards,
Ranga (7 Replies)
Discussion started by: r_W213
7 Replies
8. UNIX for Advanced & Expert Users
Dear All
jobs are scheduled in crontab . To view this I use crontab -l . But suddenly today I am not able to see any jobs that is being scheduled in crontab. when I type crontab -l , I am seeing nothing.I am not logging through admin user(i dont have it).But I can schedule jobs through... (3 Replies)
Discussion started by: tkbharani
3 Replies
9. Shell Programming and Scripting
I have a crontab entry,but it is not working.
Can anybody help me in this regard?? (2 Replies)
Discussion started by: Sourav_Paul
2 Replies
10. UNIX for Dummies Questions & Answers
Hi, can someone explain the differences between using the at and crontab commands. When would you use one command over the other?
TIA
Dom (1 Reply)
Discussion started by: domburf69
1 Replies
LEARN ABOUT DEBIAN
unparse_time
PARSE_TIME(3) BSD Library Functions Manual PARSE_TIME(3)
NAME
parse_time, print_time_table, unparse_time, unparse_time_approx, -- parse and unparse time intervals
LIBRARY
The roken library (libroken, -lroken)
SYNOPSIS
#include <parse_time.h>
int
parse_time(const char *timespec, const char *def_unit);
void
print_time_table(FILE *f);
size_t
unparse_time(int seconds, char *buf, size_t len);
size_t
unparse_time_approx(int seconds, char *buf, size_t len);
DESCRIPTION
The parse_time() function converts a the period of time specified in into a number of seconds. The timespec can be any number of <number
unit> pairs separated by comma and whitespace. The number can be negative. Number without explicit units are taken as being def_unit.
The unparse_time() and unparse_time_approx() does the opposite of parse_time(), that is they take a number of seconds and express that as
human readable string. unparse_time produces an exact time, while unparse_time_approx restricts the result to only include one units.
print_time_table() prints a descriptive list of available units on the passed file descriptor.
The possible units include:
second, s
minute, m
hour, h
day
week seven days
month 30 days
year 365 days
Units names can be arbitrarily abbreviated (as long as they are unique).
RETURN VALUES
parse_time() returns the number of seconds that represents the expression in timespec or -1 on error. unparse_time() and
unparse_time_approx() return the number of characters written to buf. if the return value is greater than or equal to the len argument, the
string was too short and some of the printed characters were discarded.
EXAMPLES
#include <stdio.h>
#include <parse_time.h>
int
main(int argc, char **argv)
{
int i;
int result;
char buf[128];
print_time_table(stdout);
for (i = 1; i < argc; i++) {
result = parse_time(argv[i], "second");
if(result == -1) {
fprintf(stderr, "%s: parse error
", argv[i]);
continue;
}
printf("--
");
printf("parse_time = %d
", result);
unparse_time(result, buf, sizeof(buf));
printf("unparse_time = %s
", buf);
unparse_time_approx(result, buf, sizeof(buf));
printf("unparse_time_approx = %s
", buf);
}
return 0;
}
$ ./a.out "1 minute 30 seconds" "90 s" "1 y -1 s"
1 year = 365 days
1 month = 30 days
1 week = 7 days
1 day = 24 hours
1 hour = 60 minutes
1 minute = 60 seconds
1 second
--
parse_time = 90
unparse_time = 1 minute 30 seconds
unparse_time_approx = 1 minute
--
parse_time = 90
unparse_time = 1 minute 30 seconds
unparse_time_approx = 1 minute
--
parse_time = 31535999
unparse_time = 12 months 4 days 23 hours 59 minutes 59 seconds
unparse_time_approx = 12 months
BUGS
Since parse_time() returns -1 on error there is no way to parse "minus one second". Currently "s" at the end of units is ignored. This is a
hack for English plural forms. If these functions are ever localised, this scheme will have to change.
HEIMDAL
October 31, 2004 HEIMDAL