Sponsored Content
Operating Systems Solaris Kill a particular process if it's over an hour hold Post 302150424 by porter on Tuesday 11th of December 2007 12:11:58 PM
Old 12-11-2007
You will have to put in the debug lines as I suggested, those ETIME formats look okay.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

2. Shell Programming and Scripting

how to start a process and make it sleep for 5 mins and then kill that process

how to start a process and make it sleep for 5 mins and then kill that process (6 Replies)
Discussion started by: shrao
6 Replies

3. Programming

kill(0,-9) don't kill the process

Hi all i have simple c program , when i wish to kill the app im using kill(0,-9) , but it seams this command don't do any thing and the program. just ignore it . what im doing wrong here ? im using HP-UX ia64 Thanks (9 Replies)
Discussion started by: umen
9 Replies

4. Shell Programming and Scripting

Kill a process without using kill command

Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies

5. Linux

Kill a process without using kill command

I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies

6. Shell Programming and Scripting

Shell Script to Kill Process(number of process) Unix/Solaris

Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies

7. Shell Programming and Scripting

grep the process id and kill all the filtered process

Hi I want to write a shell script which can find the process id's of all the process and kill them eg: ps ax | grep rv_ 3015 ? S 0:00 /home/vivek/Desktop/rv_server 3020 ? S 0:00 /home/vivek/Desktop/rv_gps 3022 ? S 0:00 /home/vivek/Desktop/rv_show ... (7 Replies)
Discussion started by: vivek_naragund
7 Replies

8. UNIX for Dummies Questions & Answers

Script to start background process and then kill process

What I need to learn is how to use a script that launches background processes, and then kills those processes as needed. The script successfully launches the script. But how do I check to see if the job exists before I kill it? I know my problem is mostly failure to understand parameter... (4 Replies)
Discussion started by: holocene
4 Replies

9. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies

10. Shell Programming and Scripting

Script for Deleting a process which exist every day in hold state

Hi All , There always exist one process in hold state every day which will cause savior impact if i didn't kill it. i will do it manually . Manul process is this. sudo -iu root/opt/app/root/cdlinux/ndm/bin/direct -- it will take me connect direct prompt Sel proc ; -- it will displays... (9 Replies)
Discussion started by: Phani369
9 Replies
_lwp_cond_wait(2)						   System Calls 						 _lwp_cond_wait(2)

NAME
_lwp_cond_wait, _lwp_cond_timedwait, _lwp_cond_reltimedwait - wait on a condition variable SYNOPSIS
#include <sys/lwp.h> int _lwp_cond_wait(lwp_cond_t *cvp, lwp_mutex_t *mp); int _lwp_cond_timedwait(lwp_cond_t *cvp, lwp_mutex_t *mp, timestruc_t *abstime); int _lwp_cond_reltimedwait(lwp_cond_t *cvp, lwp_mutex_t *mp, timestruc_t *reltime); DESCRIPTION
These functions are used to wait for the occurrence of a condition represented by an LWP condition variable. LWP condition variables must be initialized to 0 before use. The _lwp_cond_wait() function atomically releases the LWP mutex pointed to by mp and causes the calling LWP to block on the LWP condition variable pointed to by cvp. The blocked LWP may be awakened by _lwp_cond_signal(2), _lwp_cond_broadcast(2), or when interrupted by delivery of a signal. Any change in value of a condition associated with the condition variable cannot be inferred by the return of _lwp_cond_wait() and any such condition must be re-evaluated. The _lwp_cond_timedwait() function is similar to _lwp_cond_wait(), except that the calling LWP will not block past the time of day speci- fied by abstime. If the time of day becomes greater than abstime, _lwp_cond_timedwait() returns with the error code ETIME. The _lwp_cond_reltimedwait() function is similar to _lwp_cond_wait(), except that the calling LWP will not block past the relative time specified by reltime. If the time of day becomes greater than the starting time of day plus reltime, _lwp_cond_reltimedwait() returns with the error code ETIME. The _lwp_cond_wait(), _lwp_cond_timedwait(), and _lwp_cond_reltimedwait() functions always return with the mutex locked and owned by the calling lightweight process. RETURN VALUES
Upon successful completion, 0 is returned. A non-zero value indicates an error. ERRORS
If any of the following conditions are detected, _lwp_cond_wait(), _lwp_cond_timedwait(), and _lwp_cond_reltimedwait() fail and return the corresponding value: EINVAL The cvp argument points to an invalid LWP condition variable or the mp argument points to an invalid LWP mutex. EFAULT The mp, cvp, or abstime argument points to an illegal address. If any of the following conditions occur, _lwp_cond_wait(), _lwp_cond_timedwait(), and _lwp_cond_reltimedwait() fail and return the corre- sponding value: EINTR The call was interrupted by a signal or fork(2). If any of the following conditions occur, _lwp_cond_timedwait() and _lwp_cond_reltimedwait() fail and return the corresponding value: ETIME The time specified inabstime or reltime has passed. EXAMPLES
Example 1 Use the _lwp_cond_wait() function in a loop testing some condition. The _lwp_cond_wait() function is normally used in a loop testing some condition, as follows: lwp_mutex_t m; lwp_cond_t cv; int cond; (void) _lwp_mutex_lock(&m); while (cond == FALSE) { (void) _lwp_cond_wait(&cv, &m); } (void) _lwp_mutex_unlock(&m); Example 2 Use the _lwp_cond_timedwait() function in a loop testing some condition. The _lwp_cond_timedwait() function is also normally used in a loop testing some condition. It uses an absolute timeout value as follows: timestruc_t to; lwp_mutex_t m; lwp_cond_t cv; int cond, err; (void) _lwp_mutex_lock(&m); to.tv_sec = time(NULL) + TIMEOUT; to.tv_nsec = 0; while (cond == FALSE) { err = _lwp_cond_timedwait(&cv, &m, &to); if (err == ETIME) { /* timeout, do something */ break; SENDwhom} } (void) _lwp_mutex_unlock(&m); This example sets a bound on the total wait time even though the _lwp_cond_timedwait() may return several times due to the condition being signalled or the wait being interrupted. Example 3 Use the _lwp_cond_reltimedwait() function in a loop testing some condition. The _lwp_cond_reltimedwait() function is also normally used in a loop testing some condition. It uses a relative timeout value as follows: timestruc_t to; lwp_mutex_t m; lwp_cond_t cv; int cond, err; (void) _lwp_mutex_lock(&m); while (cond == FALSE) { to.tv_sec = TIMEOUT; to.tv_nsec = 0; err = _lwp_cond_reltimedwait(&cv, &m, &to); if (err == ETIME) { /* timeout, do something */ break; } } (void) _lwp_mutex_unlock(&m); SEE ALSO
_lwp_cond_broadcast(2), _lwp_cond_signal(2), _lwp_kill(2), _lwp_mutex_lock(2), fork(2), kill(2) SunOS 5.11 13 Apr 2001 _lwp_cond_wait(2)
All times are GMT -4. The time now is 06:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy