Possibly better to wrap your script as a loop, e.g.
Code:
#!/bin/ksh
lastsec=-1 # Set to an invalid second count to ensure an immediate start.
while true
do
currsec=`date +%S`
((testsec=$currsec/5))
((testsec=$testsec*5))
if [ $testsec -eq $currsec -a $testsec -ne $lastsec ]
then
run-your-code-here
else
sleep 1
fi
lastsec=$currsec
done
Of course, this never ends unless you put an exit in the code somewhere. You could consider testing for the minute to have passed and end, then schedule it with cron every minute, that way if it ever crashed out, it would be started again.
Not a great way, but it's an option. One wonders why you need to run it every five seconds. Can you enlighten us?
Anyway, I hope that this helps or gives you useful thoughts.
I scheduled 2 Oracle jobs to run on IBM AIX 4.3.3 at
06:50 and 06:58 on 02/02/03 with the below syntax:
$ at 06:50 02/02/03 /orac/ora11/temp/sun_job1.sh
Job oracle.1044175800.a will be run at Sun Feb 2 06:50:00 2003.
$ at 06:58 02/02/03 /orac/ora11/temp/sun_job2.sh
Job... (1 Reply)
Hello,
I want to know about job scheduling utilities available in unix. It should not be responsible just for starting the job like in case of cron but should also be able to handle the execution of jobs.
Regards,
Ritesh (1 Reply)
I am working on UNIX AIX system, with Oracle OS.
We are not supposed to use any tools to schedule our unix shell scripts.
Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc.
If anyone has worked/ is working... (1 Reply)
I am working on UNIX AIX system, with Oracle OS.
We are not supposed to use any tools to schedule our unix shell scripts.
Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc.
If anyone has worked/ is working... (4 Replies)
Hello All,
I want to run a script for every 5 minutes interval.So i developed a script which has to be scheduled to run for every 5 minutes. That script internally runs another script. But the problem is it is not executing properly. Can anybody throw some light on this.
Below are the code... (4 Replies)
Hi All,
I have a script which is scheduled in the Cron. It runs every 10th and 40th min of an hour.The job has to run every 30min.
But, I do not want to have the 00:10 MST run every day.Is it possible to exclude that run from the schedule?Or any other way through which i can run my job every... (4 Replies)
Hi All,
I've been trying to schedule a job using the at command on Solaris 5.10 but i've been running into some issue. ( Not allowed to use cron :wall: )
I have a script that reads a logs file, does some iteration and cat's the output in an email .
## the o/p of /home/myscript.sh is : ... (2 Replies)
Hi All,
I am new to unix and i have a task in front of me.
The code part is "android update sdk" . I need to crontab this process.
Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies
LEARN ABOUT DEBIAN
irsend
IRSEND(1) User Commands IRSEND(1)NAME
irsend - basic LIRC program to send infra-red commands
SYNOPSIS
irsend [options] DIRECTIVE REMOTE CODE [CODE...]
DESCRIPTION
Asks the lircd daemon to send one or more CIR (Consumer Infra-Red) commands. This is intended for remote control of electronic devices such
as TV boxes, HiFi sets, etc.
DIRECTIVE can be:
SEND_ONCE - send CODE [CODE ...] once
SEND_START - start repeating CODE
SEND_STOP - stop repeating CODE
LIST - list configured remote items
SET_TRANSMITTERS - set transmitters NUM [NUM ...]
SIMULATE - simulate IR event
REMOTE is the name of a remote, as described in the lircd configuration file.
CODE is the name of a remote control key of REMOTE, as it appears in the lircd configuration file.
NUM is the transmitter number of the hardware device.
For the LIST DIRECTIVE, REMOTE and/or CODE can be empty:
LIST "" "" - list all configured remote names
LIST REMOTE "" - list all codes of REMOTE
LIST REMOTE CODE - list only CODE of REMOTE
The SIMULATE command only works if it has been explicitly enabled in lircd.
-h --help
display usage summary
-v --version
display version
-d --device
use given lircd socket [/var/run/lirc/lircd]
-a --address=host[:port]
connect to lircd at this address
-# --count=n
send command n times
EXAMPLES
irsend LIST DenonTuner ""
irsend SEND_ONCE DenonTuner PROG-SCAN
irsend SEND_ONCE OnkyoAmpli VOL-UP VOL-UP VOL-UP VOL-UP
irsend SEND_START OnkyoAmpli VOL-DOWN ; sleep 3
irsend SEND_STOP OnkyoAmpli VOL-DOWN
irsend SET_TRANSMITTERS 1
irsend SET_TRANSMITTERS 1 3 4
irsend SIMULATE "0000000000000476 00 OK TECHNISAT_ST3004S"
FILES
/etc/lirc/lircd.conf
Default lircd configuration file. It should contain all the remotes, their infra-red codes and the corresponding timing and wave-
form details.
DIAGNOSTICS
If lircd is not running (or /var/run/lirc/lircd lacks write permissions) irsend aborts with the following diagnostics:
"irsend: could not connect to socket"
"irsend: Connection refused" (or "Permission denied").
SEE ALSO
The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory.
lircd(8), mode2(1), smode2(1), xmode2(1), irrecord(1), irw(1), http://www.lirc.org.
irsend 0.9.0-pre1 October 2010 IRSEND(1)