Sponsored Content
Full Discussion: process not getting killed
Top Forums UNIX for Dummies Questions & Answers process not getting killed Post 67668 by finster on Friday 25th of March 2005 12:49:14 AM
Old 03-25-2005
I didn't see it respond to truss, but I don't remember what options were used.

Shouldn't it respond to a truss regardless? Is it common for it not to?

I will try another truss but what are the best truss options to use(unfamilar) - truss -aef <PID> ?

Also , should I do a core dump for the process(gcore)?

I suspect a reboot will fix it, but just trying to find out what caused the issue.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Who is the parent of a killed process ?

Suppose we have the following process tree: init-> ProcessA->processB->processC then I kill processB Who is the parent of the processC? init or the processA (6 Replies)
Discussion started by: Puntino
6 Replies

2. Programming

how to delay a process from getting killed

We are forking a process B from process A and the process B should display the details it reads from process C(daemon process) continuously. Let us say that the process C sents 100 packets.The process B receives all the 100 packets from the process C before it prints all details of 31... (1 Reply)
Discussion started by: cijkmysj
1 Replies

3. Solaris

how to run a killed process

hi, i am creating a daemon process for updating the file at regular interval.one problem with this is if anybody kills the daemon it wont update the file.anybody have idea how to rerun the daemon if it killed.the code is written in c++ in solaries environment. thnaks & regards suresh (8 Replies)
Discussion started by: suresh_rtp
8 Replies

4. Shell Programming and Scripting

Sybase Process Killed - How to identify

I have this shell script and in case the sybase process is been killed how can identify whether the process was killed or not, as the error code always returns 0. #!/bin/sh isql -S SERVER -U user -P pass<<TOP select * from tableName go TOP echo $? (2 Replies)
Discussion started by: dinjo_jo
2 Replies

5. Solaris

LDAP process getting killed

Hi all, Currently I am using LDAP to store some network related data, When I run following script ./ns-slapd ldif2db Execution of above script terminates displaying "Killed" on the console. As far as I know, a process can be killed by two ways- 1. manually running " kill -9 <PID of LDAP... (1 Reply)
Discussion started by: akash_mahakode
1 Replies

6. UNIX for Dummies Questions & Answers

SAS Process Getting Killed

HI all, I am very new to AIX (matter of fact Unix). We are currently automating out manual process using Unix Shell Scripting. My wrote a shell script which will accept the name of the sas job as parameter, checks the existense of the sas file in the specified folder. If it is not present,... (1 Reply)
Discussion started by: anubhav2020
1 Replies

7. UNIX for Dummies Questions & Answers

Protect a Process from Being Killed

Hi, I have a process which takes 13-15 mins for execution and its getting killed in the meantime.So can you please helpme out how to protect the process from getting killed. Thanks in advance. Regards, Harika (9 Replies)
Discussion started by: harikagrp
9 Replies

8. UNIX for Dummies Questions & Answers

Process Killed : Need to find why ?

Hi reader, I'm making a tool out of korn shell script that is running on a HP-UX server. But everytime i invoke the tool, it gets killed after a while (mid-process). I have tried re-running it a couple of times but each invocation ending up the same way .. following is a snippet of the o/p... (8 Replies)
Discussion started by: clakkad
8 Replies

9. Shell Programming and Scripting

how to prevent process from being killed

Hi,all.Well,I know someone has already asked this question before,however,It's too long before.So i post a new thread here. Here is the issue.I have a shell script that use awk to calculate something and the script takes about 15 mins,it will use 100% CPU,and the system automatically killed the... (2 Replies)
Discussion started by: homeboy
2 Replies

10. Shell Programming and Scripting

Capturing the killed process logs

I have two set of questions. 1) To skip killing some process automatically. 2) To kill other process and capture their log. I have set of process, some needs to be killed gracefully and others should be skipped. Listed are the process. adm 1522... (1 Reply)
Discussion started by: murali1687
1 Replies
ppriv(1)																  ppriv(1)

NAME
ppriv - inspect or modify process privilege sets and attributes SYNOPSIS
/usr/bin/ppriv -e [-D | -N] [-s spec] command [arg...] /usr/bin/ppriv [-v] [-S] [-D | -N] [-s spec] [pid | core] ... /usr/bin/ppriv -l [-v] [privilege-specification...] The first invocation of the ppriv command runs the command specified with the privilege sets and flags modified according to the arguments on the command line. The second invocation examines or changes the privilege state of running process and core files. The third invocation lists the privileges defined and information about specified privileges or privileges set specifications. The following options are supported: -D Turns on privilege debugging for the processes or command supplied. -e Interprets the remainder of the arguments as a command line and runs the command line with specified privilege attributes and sets. -l Lists all currently defined privileges on stdout. -N Turns off privilege debugging for the processes or command supplied. -s spec Modifies a process's privilege sets according to spec, a specification with the format [AEILP][+-=]privsetspec, containing no spa- ces, where: AEILP Indicates one or more letters indicating which privilege sets to change. These are case insensitive, for example, either a or A indicates all privilege sets. +-= Indicates a modifier to respectively add (+), remove (-), or assign (=) the listed privileges to the specified set(s) in privsetspec. privsetspec Indicates a comma-separated privilege set specification (priv1,priv2, and so on), as described in priv_str_to_set(3C). Modifying the same set with multiple -s options is possible as long as there is either precisely one assignment to an individual set or any number of additions and removals. That is, assignment and addition or removal for one set are mutually exclusive. -S Short. Reports the shortest possible output strings for sets. The default is portable output. See priv_str_to_set(3C). -v Verbose. Reports privilege sets using privilege names. The ppriv utility examines processes and core files and prints or changes their privilege sets. ppriv can run commands with privilege debugging on or off or with fewer privileges than the invoking process. When executing a sub process, the only sets that can be modified are L and I. Privileges can only be removed from L and I as ppriv starts with P=E=I. ppriv can also be used to remove privileges from processes or to convey privileges to other processes. In order to control a process, the effective set of the ppriv utility must be a super set of the controlled process's E, I, and P. The utility's limit set must be a super set of the target's limit set. If the target's process uids do not match, the {PRIV_PROC_OWNER} privilege must be asserted in the utility's effective set. If the controlled processes have any uid with the value 0, more restrictions may exist. See privileges(5). Example 1: Obtaining the Process Privileges of the Current Shell example$ ppriv $$ 387: -sh flags = <none> E: basic I: basic P: basic L: all Example 2: Removing a Privilege From Your Shell's Inheritable and Effective set example$ ppriv -s EI-proc_session $$ The subprocess can still inspect the parent shell but it can no longer influence the parent because the parent has more privileges in its Permitted set than the ppriv child process: example$ truss -p $$ truss: permission denied: 387 example$ ppriv $$ 387: -sh flags = <none> E: basic,!proc_session I: basic,!proc_session P: basic L: all Example 3: Running a Process with Privilege Debugging example$ ppriv -e -D cat /etc/shadow cat[418]: missing privilege "file_dac_read" (euid = 21782), needed at ufs_access+0x3c cat: cannot open /etc/shadow The privilege debugging error messages are sent to the controlling terminal of the current process. The "needed at" address specification is an artifact of the kernel implementation and it can be changed at any time after a software update. The system call number can be mapped to a system call using /etc/name_to_sysnum. Example 4: Listing the Privileges Available in the Current Zone This example lists the privileges available in the current zone (see zones(5)). When run in the global zone, all defined privileges are listed. example$ ppriv -l zone ... listing of all privileges elided ... Example 5: Examining a Privilege Aware Process The following example examines a privilege aware process: example$ ppriv -S `pgrep rpcbind` 928: /usr/sbin/rpcbind flags = PRIV_AWARE E: net_privaddr,proc_fork,sys_nfs I: none P: net_privaddr,proc_fork,sys_nfs L: none See setpflags(2) for explanations of the flags. The following exit values are returned: 0 Successful operation. non-zero An error has occurred. /proc/* Process files /etc/name_to_sysnum system call name to number mapping See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The invocation is Evolving. The output is Unstable. gcore(1), truss(1), setpflags(2), priv_str_to_set(3C), proc(4), attributes(5), privileges(5), zones(5) 15 Mar 2005 ppriv(1)
All times are GMT -4. The time now is 05:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy