12-18-2015
Hi RudiC,
Quote:
You can either have the job terminate itself using e.g. a timer/counter
Can you please suggest as how to terminate the job itself by using counter/timer?
Thanks-
Pokhraj Das
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have the below crontab job that it will run at every 7:00am - 10:00am , it work fine , now if I want to skip to run the crontab job at a specific time , eg. I want the script not to run at next Monday 8:00am ( only skip this time , other time is normal ) , how can I make it ? is it possible ?... (3 Replies)
Discussion started by: ust
3 Replies
2. Shell Programming and Scripting
I have a perl script, when I ran manually it works perfect. I check the permissions which are fine.
How can I find out why it is not running? how can I setup a log to check.
I am running it on solaris 9.
It compares multiple files, SCP and then send out an e-mail.
As I said when I ran it... (2 Replies)
Discussion started by: amir07
2 Replies
3. UNIX for Advanced & Expert Users
Hi, new to this forum and not sure if this is the right place to post. I'm new to cron jobs and scripts, and I need some help with a script to be used with a cron job. I already have a bot set up at a certain website address and need a script that the cron job will load every day that tells it to... (1 Reply)
Discussion started by: klawless
1 Replies
4. Shell Programming and Scripting
Hi
I need to run a script every five minutes and it should run between 07-15 hours all days.
How i can achieve this...
i tried like this
*/5 07-15 * * * /scripts/CreateFtpData.sh
It throws an error... (1 Reply)
Discussion started by: aemunathan
1 Replies
5. Solaris
How to setup a cron job to run every 45 minutes in Solaris 5.10 (9 Replies)
Discussion started by: reyazan
9 Replies
6. UNIX for Advanced & Expert Users
my colleague was asking about this:
is there a way to run a cron job biweekly, like a script five.sh
to run every *OTHER* Friday within November
its part about every other Friday we cant find any documentation.
thx
L (8 Replies)
Discussion started by: lydiaflamp
8 Replies
7. Shell Programming and Scripting
Hi,
First of all merry christmas and Happy holidays to all :D
My situation is as below,
When a backup job runs on a mainframe server, it creates a 0byte file on a network drive which is accessible through linux
Linux server : Red Hat Enterprise Linux Server release 5.3 Beta (Tikanga)
File... (6 Replies)
Discussion started by: sam05121988
6 Replies
8. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
9. Shell Programming and Scripting
Hello Gurus,
I want to schedule a cron job which will run every 2 minutes starts at 11:25 AM and 3:25 AM daily.
Can you please suggest as how to schedule the job.
Thanks-
Pokhraj Das (2 Replies)
Discussion started by: pokhraj_d
2 Replies
10. Shell Programming and Scripting
Hi,
I created this cron job for asterisk to send sms daily to a number
#!/bin/sh
#custom mod - send sms once a day, at 07:00.
CRON_PATH="/etc/asterisk/gw/crontabs_root";
if ! grep 'gsm send sms' $CRON_PATH > /dev/null 2>&1 ;then
echo "* 7 * * * asterisk -rx 'gsm send sms 1 7666... (4 Replies)
Discussion started by: jazzyzha
4 Replies
LEARN ABOUT NETBSD
timer_settime
TIMER_SETTIME(2) BSD System Calls Manual TIMER_SETTIME(2)
NAME
timer_settime, timer_gettime, timer_getoverrun -- process timer manipulation
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <time.h>
int
timer_settime(timer_t timerid, int flags, const struct itimerspec * restrict tim, struct itimerspec * restrict otim);
int
timer_gettime(timer_t timerid, struct itimerspec *tim);
int
timer_getoverrun(timer_t timerid);
DESCRIPTION
The timer_settime() sets the next expiration time of the timer with ID timerid to the it_value (see itimerspec(3)) specified in the tim argu-
ment. If the value is 0, the timer is disarmed. If the argument otim is not NULL the old timer settingas are returned.
If the flags argument is set to TIMER_RELTIME then the expiration time is set to the value in nanoseconds specified in the tim argument from
the time the call to timer_settime() was made. If the flags argument is set to TIMER_ABSTIME then the expiration time is set to be equal to
the difference between the clock associated with this timer, and the value specified in the tim argument. If that time has already passed,
then the call succeeds, and the expiration notification occurs.
If the it_interval of the tim argument is non-zero, then the timer reloads upon expiration.
The timer_gettime() function returns the current settings of the timer specified by the timerid argument in the tim argument.
Only one notification event (signal) can be pending for a given timer and process. If a timer expires while the signal is still queued for
delivery, then the overrun counter for that timer is increased. The counter can store values up to DELAYTIMER_MAX. When the signal is
finally delivered to the process, then the timer_getoverrun() function can be used to retrieve the overrun counter for the timer specified in
the timerid argument.
NOTES
Expiration time values are always rounded up to the resolution of the timer, so a notification will never be sent before the requested time.
Values returned in the otim argument of timer_settime() or in the tim argment of timer_gettime() are subject to the above rounding effect and
might not exactly match the requested values by the user.
RETURN VALUES
If successful, the timer_gettime() and timer_settime() functions return 0, and the timer_getoverrun() function returns the expiration overrun
count for the specified timer. Otherwise, the functions return -1, and set errno to indicate the error.
ERRORS
The timer_gettime(), timer_getoverrun(), and timer_settime() functions will fail if:
[EINVAL] The argument timerid does not correspond to a valid timer id as returned by timer_create() or that timer id has been
deleted by timer_delete().
The timer_settime() function will fail if:
[EINVAL] A nanosecond field in the tim structure specified a value less than zero or greater than or equal to 10e9.
SEE ALSO
clock_gettime(2), timer_create(2), timer_delete(2)
STANDARDS
IEEE Std 1003.1b-1993 (``POSIX.1''), IEEE Std 1003.1i-1995 (``POSIX.1'')
BSD
May 17, 2010 BSD