01-30-2007
Dear
it is the same server that i am facing the problem in. but it seems that the terminal that is directly connected to the console port of the server cam not logoff so how can i force the logoff without restarting the server.
later i will provide the rc.dt, i dont have access now.
thanks for your help
8 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
TKILL(1) LAM TOOLS TKILL(1)
NAME
tkill - Terminate LAM on one node.
SYNOPSIS
tkill [-dhvN] [-f killfile]
OPTIONS
-d Turn on debugging mode. This implies -v.
-h Print the command help menu.
-v Be verbose.
-N Pretend; do not take action.
-f killfile Use killfile as the name of the kill file.
DESCRIPTION
The tkill tool terminates the LAM session started by hboot(1) on the local node. tkill makes use of a kill file created by the LAM kernel,
which contains the process identifiers of every LAM process in ASCII format. A SIGHUP (see signal(3)) signal is sent to every process
listed in the kill file. tkill waits a short period of time for each process to die. By adding the debug option, the user can see the
final disposition of each process. The mission is accomplished if all processes end up dead.
In LAM, the first process to be killed is always the kernel. When the kernel receives its termination signal, it propagates the signal to
all of its constituent processes. Therefore, tkill will ordinarily be racing the kernel to kill all other processes. This redundant
aspect of tkill allows it to be used as a general purpose tool in association with hboot(1).
FILES
/tmp/lam-$USER@hostname the kill file, created by the kernel, where $USER is the userid, and hostname is the name of the local
machine
SEE ALSO
hboot(1), lam-helpfile(5)
LAM 7.1.4 July, 2007 TKILL(1)