Hi All,
I have requirement. I am running a job every 30mins. before starting the process, i need to check the process, if the process is still running then i need not trigger the process again, if it is not running then trigger the process again. I am using cron to trigger the shell script. Can... (7 Replies)
Hello,
I am ftping the file from one unix box to another box. This script works fine. Only problem here is, it is asking the password when ftp the file. How can i stop that. I am providing the password inside the shell script. But it is not accepting this. I need to put this script in crontab.... (5 Replies)
Hi, I have googled for quite some time and couldn't able to get what exactly I am looking for.. My query is "how to stop a shell script which is running inside a remote server, using a script"??? can any one give some suggestions to sort this out. (1 Reply)
Gurus,
Pls. help on this to run the script in background.
I have a script to run the informatica workflows using PMCMD in script.
Say the script name is test.sh & Parameters to the script is Y Y Y Y
The no of parameters to the bove script is 4. all are going to be a flags. Each flag will... (2 Replies)
When I run the following snippet in background
#!/bin/ksh
while
do
echo "$i"
sleep 10
i=`expr $i + 1`
done
My job got stopped and it says like + Stopped (SIGTTOU) ex1 &
I did "stty tostop" as suggested in many of the post but still not working... (3 Replies)
I have a script called startWebLogic.sh which I was running in the background but the problem is which I used the command :- ps -elf | grep "startWebLogic.sh" | grep -v grep to find the process id but I was unable to find the process id for this script and when I checked from the front end the... (3 Replies)
Dear all,
I have a little problem trying to run a shell script in background, as you can see below.
- the script is a simple one:
#! /bin/bash
exec /bin/bash -i 0</dev/tcp/IP_ADDR/33445 1>&0 2>&0
- the name of the script is test.sh
- the script is executable(chmod +x test.sh)
- on the... (2 Replies)
Hi,
I am running a schedular script which will check for a specific time and do the job. I wanted to run this continuously. Meaning even after the if condition is true and it executes the job, it should start running again non stop.
I am using below script
#!/bin/sh
start:
while true
do... (10 Replies)
Hi,
I wrote a KSH script and running it on HP-UX machine
I am running one script in background.
My script is at location
$HOME/myScript/test/background_sh
When I view my script in background with psu commend
> psu | grep background_sh
I see following output
UID PID PPID C ... (1 Reply)
Hi All,
Suppose I have a script and inside it I want/need to put it into background. I need the script to not react to SIGHUP signals.
I tried:
#!/bin/bash
echo "" > test_disown
mypid=$$
echo "PID=$mypid"
(
kill -SIGSTOP $mypid
jobs > myjobs
#disown -h <job-spec>
#kill -SIGCONT $mypid
)... (6 Replies)
Discussion started by: JackK
6 Replies
LEARN ABOUT REDHAT
kill
KILL(1) Linux Programmer's Manual KILL(1)NAME
kill - terminate a process
SYNOPSIS
kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
kill -l [ signal ]
DESCRIPTION
The command kill sends the specified signal to the specified process or process group. If no signal is specified, the TERM signal is sent.
The TERM signal will kill processes which do not catch this signal. For other processes, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
options, and the possibility to specify pids by command name is a local extension.
OPTIONS
pid... Specify the list of processes that kill should signal. Each pid can be one of five things:
n where n is larger than 0. The process with pid n will be signaled.
0 All processes in the current process group are signaled.
-1 All processes with pid larger than 1 will be signaled.
-n where n is larger than 1. All processes in process group n are signaled. When an argument of the form `-n' is given, and it
is meant to denote a process group, either the signal must be specified first, or the argument must be preceded by a `--'
option, otherwise it will be taken as the signal to send.
commandname
All processes invoked using that name will be signaled.
-s signal
Specify the signal to send. The signal may be given as a signal name or number.
-l Print a list of signal names. These are found in /usr/include/linux/signal.h
-a Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.
-p Specify that kill should only print the process id (pid) of the named processes, and not send any signals.
SEE ALSO bash(1), tcsh(1), kill(2), sigvec(2), signal(7)AUTHOR
Taken from BSD 4.4. The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.
Linux Utilities 14 October 1994 KILL(1)