Yeah... Don's right.. We could have set a working directory at beginning of the script. That would save all the confusions. Add some logging too Helps in debugging
Code:
#!/bin/bash
EXEC_DIR=/home/sam
cd $EXEC_DIR
/bin/bash $EXEC_DIR/chk_job_end.sh &
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)
Hello All,
I would like to know if it is possible to launch a job in background for infinite time.
example:
myScript.ksh
while true
do
( echo "(`date`)"; top -U user | grep 'Memory:' ) >> log &
sleep 1800
done
and when i do... (5 Replies)
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)
The script checks for free space stats on Oracle. If there are any tablespaces with more than 85% usage it prints the details of the tablespace. If all the tablespaces have more than 15% free space, then "All tablespaces have more than 15 pct free space" must be printed on the screen.
When I run... (2 Replies)
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)
Hi,
Should the user jobs specified in crontab be running in background?
Cron daemon is already running in background. So I am not sure
whether should the jobs (output and error messages are redirected to file)
ran by it be explicitly stated to be run in background (& at end of command)
if one... (1 Reply)
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)
Hello Gurus,
I have a requirement to run a job from cron only for 30 minutes duration daily twice at 8.35 am and 20.35 pm
Can you please suggest how to schedule the job?
Thanks-
Pokhraj (5 Replies)
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)
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 DEBIAN
qsig
qsig(1B) PBS qsig(1B)NAME
qsig - signal pbs batch job
SYNOPSIS
qsig [-s signal] job_identifier ...
DESCRIPTION
The qsig command requests that a signal be sent to executing batch jobs. The signal is sent to the session leader of the job.
If the -s option is not specified, `SIGTERM' is sent. The request to signal a batch job will be rejected if:
- The user is not authorized to signal the job.
- The job is not in the running state.
- The requested signal is not supported by the system upon which the job is executing.
The qsig command sends a Signal Job batch request to the server which owns the job.
OPTIONS -s signal Declares which signal is sent to the job.
The signal argument is either a signal name, e.g. SIGKILL, the signal name without the SIG prefix, e.g. KILL, or a unsigned
signal number, e.g. 9. The signal name SIGNULL is allowed; the server will send the signal 0 to the job which will have no
effect on the job, but will cause an obituary to be sent if the job is no longer executing. Not all signal names will be
recognized by qsig. If it doesn't recognize the signal name, try issuing the signal number instead.
Two special signal names, "suspend" and "resume", are used to suspend and resume jobs. Cray systems use the Cray-specific
suspend()/resume() calls.
On non-Cray system, suspend causes a SIGTSTP to be sent to all processes in job's top task, wait 5 seconds, and then send a
SIGSTOP to all processes in all tasks on all nodes in the job. This differs from TORQUE 2.0.0 which did not have the abil-
ity to propogate signals to sister nodes. Resume sends a SIGCONT to all processes in all tasks on all nodes.
When suspended, a job continues to occupy system resources but is not executing and is not charged for walltime. The job
will be listed in the "S" state. Manager or operator privilege is required to suspend or resume a job.
Note that interactive jobs may not resume properly because the top-level shell will background the suspended child process.
OPERANDS
The qsig command accepts one or more job_identifier operands of the form: sequence_number[.server_name][@server]
STANDARD ERROR
The qsig command will write a diagnostic messages to standard error for each error occurrence.
EXIT STATUS
Upon successful processing of all the operands presented to the qsig command, the exit status will be a value of zero.
If the qsig command fails to process any operand, the command exits with a value greater than zero.
SEE ALSO qsub(1B), pbs_sigjob(3B), pbs_resources_*(7B) where * is system type, and the PBS ERS.
Localqsig(1B)
12-27-2013
Helps in debugging