07-19-2006
what happens if you just kill the parent script?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I should know this, but do K scripts in the /etc/rc?.d directories get run in numerically ascending or descending order? By default there are none in rc3.d. Is it OK to put 2 in there, and will they be run first (which is my goal).
Thanks,
Chuck (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. UNIX for Advanced & Expert Users
We have a bunch of tools, that run on linux and on unix, I've got start up scripts that bring up their license managers when the unix box boots, do I need kill scripts for when the box is shutting down? I've not seen much documentation on this, just on getting the license managers started, but... (1 Reply)
Discussion started by: kymberm
1 Replies
3. Shell Programming and Scripting
Hi,
I have a strange problem.
In my shell script, i am startting another program (a c++ exe) with nohup .
I am getting the process id of this started process with using $!
I am writing this process id into another file so that i can keep checking for this process ids to check whether the... (2 Replies)
Discussion started by: parvathi_rd
2 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I have to perform an audit of a system at work and I am looking at its /etc/rc3.d:
K01tog-pegasus K74nscd S08iptables S50openemm
K01yum K74ntpd S09isdn S55cups
K02NetworkManager K85mdmpd S09pcmcia S55sshd
K03rhnsd ... (8 Replies)
Discussion started by: mojoman
8 Replies
5. Shell Programming and Scripting
echo "Hi $username, guess what my favourite colour is!"
count=0
while ]
do
read colour
if
then
$count=1
echo "See ya later!"
elif
then
$count=1
echo "You guessed correctly! Great job!"... (6 Replies)
Discussion started by: solomonsnare
6 Replies
6. Shell Programming and Scripting
Shell : bash
OS : Oracle Linux 6.4
I want to save the ouput of a nohup command to file other than nohup.out . Below are my 3 attempts.
For both Attempt1 and Attempt2 , the redirection logs the output correctly to the output file. But I get the error "ignoring input and redirecting stderr to... (7 Replies)
Discussion started by: kraljic
7 Replies
7. Shell Programming and Scripting
Hello,
I want to save pid of a child process but I get empty file.
su myuser -c "nohup ./mydaemon.sh >/dev/null 2>&1 & print $! > mydaemon.pid"
This one works:
nohup ./mydaemon.sh >/dev/null 2>&1 & print $! > mydaemon.pid
Please help. Thank you in advance. (2 Replies)
Discussion started by: vincegata
2 Replies
8. Shell Programming and Scripting
Hi,
I have a query related to UNIX Crontab scripts -
Issue: Server space on the db server got 100% full as a result of which the cron scripts did not run. The space utilization issue got resolved in the afternoon. The crons scheduled for a time post the resolution caught up. However the... (1 Reply)
Discussion started by: qwerty000
1 Replies
9. Shell Programming and Scripting
Hi there!
I have a tricky problem concerning a nohup process:
I started a python2.7 script which loops over a function.
At the end it restarts the function. Due to a mistake I'm now having a never ending nohup process that I have to kill.
I started the program execution with:
>>nohup... (4 Replies)
Discussion started by: Lydia
4 Replies
10. Shell Programming and Scripting
I have a need to run any number of identical scripts simultaneously, so I've created a driver script which reads a template script, edits these appropriately and then submits them via nohup. The spawned scripts all check to see at some point how many of their number are running and once the count... (7 Replies)
Discussion started by: safedba
7 Replies
KILL(1) BSD General Commands Manual KILL(1)
NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the process(es) specified by the pid operand(s).
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
Display the name of the signal corresponding to exit_status. exit_status may be the exit status of a command killed by a signal (see
the special sh(1) parameter '?') or a signal number.
If no operand is given, display the names of all the signals.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following pids have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
0 Broadcast the signal to all processes in the current process group belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill argu-
ments. See csh(1) for details.
SEE ALSO
csh(1), pgrep(1), pkill(1), ps(1), kill(2), sigaction(2), signal(7)
STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 6 AT&T UNIX.
BSD
April 28, 1995 BSD