8 More Discussions You Might Find Interesting
1. Red Hat
This issue could happen to any other service but in this case its commssioning Postfix - it seems i can't stop postfix as the PID relates to another service - i've delete the 'master.lock' but to no available - any ideas, memeory commands etc ?
thanks in advance
ps. the serve is in Production so... (2 Replies)
Discussion started by: stevie_velvet
2 Replies
2. UNIX for Dummies Questions & Answers
Hi Gurus,
I am debugging a script. it loops filelist. since the list a very long. when debugging, I only can see the last a few lines. is there any way to stop debuger in the mid of process.
the command I used for debugging is:
ksh -x scriptName
Thanks in advance (7 Replies)
Discussion started by: ken6503
7 Replies
3. Shell Programming and Scripting
Hi, I have a parallelized Mathematica program that spans across 8 MathKernels processes running at 100% and one MathKernel (highlighted in blue) running at < 10% that controls the other 8. They look like this on the cluster:
https://www.unix.com/attachment.php?attachmentid=5111&stc=1&d=1381245618... (2 Replies)
Discussion started by: giovform
2 Replies
4. Shell Programming and Scripting
Hi all,
I have tried the below code to execute.
#! /bin/bash
date1=`date -d "today 08:00:00" +%s`
date2=`date -d "today 08:01:00" +%s`
path=/home/user01/red/IDC/sample
cd $path
java Cspsamp 111.19.5.172 7025 rd1 rd1 "5022=Query|5026=109378|4=627|5=E:VD|5042=$date1|5049=$date2"... (5 Replies)
Discussion started by: aish11
5 Replies
5. UNIX for Dummies Questions & Answers
I have the following log file running since yesterday and its consuming so much of the disk space.
-rw-rw-r-- 1 dev dba 4543237120 Nov 10 09:00 load_run_file1_0.1111091224.lg
How do i kill this process. I don't have any idea of stopping this. Any help would be really appreciated.
... (3 Replies)
Discussion started by: bobby1015
3 Replies
6. Shell Programming and Scripting
I have this "process keepalive" script:
#!/bin/bash
PIDFILE=/tmp/php.pid
PHPSCRIPT=/home/www/mydomain.com/subdomains/www/parser.php
echo 'Checking php process from PID file'
if ; then
PID=`cat $PIDFILE`
if ps ax | grep -v grep | grep $PID > /dev/null
then
echo "php process still... (4 Replies)
Discussion started by: LukasB
4 Replies
7. Shell Programming and Scripting
Hi there,
I have written a script to check daily process,
each script is in a different directory.
Now the first process is running fine, when it goes to the next directory the process doesn't executes.
cd result/logs
ref=month_1888.log
echo $ref>> $logfile
cd /max/tot/first... (3 Replies)
Discussion started by: NehaKrish
3 Replies
8. Shell Programming and Scripting
Hi ,
I have a situation, where I have 10 indivudal processess started by similar instance.I say similar instance because each of them being started as a new thread:
Say I've following unix process running
process1_ADAP
process2_ADAP
process3_ADAP
Current scenario:
Now I have SHUTDOWN... (5 Replies)
Discussion started by: braindrain
5 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
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
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)