Sponsored Content
Top Forums UNIX for Advanced & Expert Users how to identify running threads using commands Post 302241343 by ynilesh on Monday 29th of September 2008 06:32:53 AM
Old 09-29-2008
lsof command shows you current opened files and threads.

Code:
lsof

- nilesh
 

10 More Discussions You Might Find Interesting

1. Solaris

Number of threads running

Is there any command to find 1) the number of threads running 2) kernel boot mode in solaris box (2 Replies)
Discussion started by: vickylife
2 Replies

2. UNIX for Dummies Questions & Answers

Running two commands in one line

hi! how do i run 2 command from the same line e.g: 'which screen' and then ls -la 'which screen' (4 Replies)
Discussion started by: rdns
4 Replies

3. Shell Programming and Scripting

Return code for parallel running threads

Hi, How to use the return code, for parallel running threads. Ex- grep pattern1 file1 file2 file3 file4 & grep pattern1 file5 file6 file7 file8 & grep pattern1 file9 file10 file11 file12 & return_code=$? if (return_code -eq 0) then echo "pattern found" else echo... (2 Replies)
Discussion started by: jitendriya.dash
2 Replies

4. Shell Programming and Scripting

Script to identify logged users & commands executed

Hi All, I am trying to write a script to get the user information & the command executed. I tried something like this : w | sort | awk '{print$5$6$7}' My requirement is to identify the users who execute the same command at same time. I need the user name & the... (2 Replies)
Discussion started by: vijayarajvp
2 Replies

5. Shell Programming and Scripting

Running sed commands

Hello I need to run some sed commands but it involves "/" in the substitute or delete, any ideas how I get round the problem. Example: cat file1.txt | sed -e '/</Header>/d' > file2.txt This errors due to the forward slash before the Header text. Thanks (3 Replies)
Discussion started by: Dolph
3 Replies

6. UNIX for Advanced & Expert Users

How to determine the number of NFS threads RUNNING on the system

Hi, Anyone can tell me how to get the number of NFS threads RUNNING on the system for Solaris 10? Someone told me for Solaris 9, the method is "echo "*svc$<svcpool" | adb -k. But, I've tried to google the method for Solaris 10 and did not find the corresponding method, please help... (1 Reply)
Discussion started by: wang.caiqi
1 Replies

7. AIX

How to list all threads in a running process

Hello, On Linux, I can use 'ps -efL | grep process_name' to list all threads that belong to a running process. -L has a different meaning on AIX and I could not find an equivalent flag in the man pages. Does anyone know of a way to dump the threads under a running process? Thanks,... (2 Replies)
Discussion started by: makodarear
2 Replies

8. AIX

How to Identify long running unix processes

Hi All, Need an urgent help, I have a requirement to find long running unix processes.. I have tried the below commands, but not succeed. I need to arrange the unix processess in an order of elapsed time (high to low) that runs in a system. For Eg: Consider we have 3 processes, Pid 1 pid 2... (5 Replies)
Discussion started by: mohamedirfan
5 Replies

9. UNIX for Advanced & Expert Users

How to check number of threads running per processor in Linux machine?

I have a machine which has 32 processor but i am really not sure how many threads are running. It has hyperthreading enabled. Is there a way i can find that all 32 processors are being used and how many threads are there in my linux box. Its a 64 bit processor. I am having very high load average... (3 Replies)
Discussion started by: Moon1234
3 Replies

10. Solaris

Failed to identify flash rom on Sunfire V240 running Solaris 10

Hi Guys, I have performed OBP & ALOM upgrade on V240 system. One of my system, running Solaris 10, having issue to identify flash rom during ALOM 1.6.10 version upgrade (OBP upgraded to latest one). May I know what the reason of this error and how can I fix it so I can upgrade ALOM using... (0 Replies)
Discussion started by: myrpthidesis
0 Replies
checkrestart(1) 						  debian-goodies						   checkrestart(1)

NAME
checkrestart - check which processes need to be restarted after an upgrade SYNOPSIS
checkrestart [ -hvpa ] [ -b blacklist_file ] [ -i package_name ] DESCRIPTION
The checkrestart program tries to determine if there are processes in the system that need to be restarted after a system upgrade. This is necessary since an upgrade will usually bring new system libraries and running processes will be still using the old versions of the libraries. In stable Debian GNU/Linux systems this is typically needed to eliminate a system exposure to a vulnerability which might have been fixed by upgrading a library which that process makes use of. Consequently, checkrestart is sometimes used as an audit tool to find outdated versions of libraries in use, particularly after security upgrades. Administrators should not, however, rely on its output completely (see BUGS below). This script needs to run as root in order to obtain the information it needs for analysis. OPTIONS
-h,--help Show the program help and exit. -v,--verbose Generate detailed output. This output includes the list of all processes found using deleted files or descriptors as well as the deleted files and descriptors found. -p,--package Only process deleted files that belong to a package, ignoring deleted files which do not have an associated package in the package system. -a,--all Process all deleted files regardless of location. This makes the program analyse deleted files even if they would be discarded because they are located in locations, such as /tmp , which are known to produce false positives. It will take preceded if used simultaneously with the -p option. -b file,--blacklist=file Read a blacklist of regular expressions from file. Any files matching the patterns will be ignored. -i name,--ignore=name Ignore services that are associated to the package name provided in name. EXIT STATUS
The program will exit with error (1) if a non-root user tries to run it. Otherwise, it will always exit with error status 0. BUGS
This program might fail if the output of the lsof utility changes since it depends on it to detect which deleted files are used by pro- cesses. It might also output some false positives depending on the processes' behaviour since it does not check yet if the (deleted) files in use are really libraries. If you find a false positive in checkrestart please provide the following information when submitting a bug report: -- The output of checkrestart using the -v (verbose) option. -- The output of running the following command as root: lsof | egrep 'delete|DEL|path inode' Checkrestart is also sensitive to the kernel version in use. And might fail to work with newer (or older) versions. A rewrite to make it less dependent on lsof could improve this, however. SEE ALSO
lsof(8) AUTHOR
checkrestart was written by Matt Zimmerman for the Debian GNU/Linux distribution. COPYRIGHT AND LICENCE
Copyright (C) 2001 Matt Zimmerman <mdz@debian.org> Copyright (C) 2007,2010-2011 Javier Fernandez-Sanguino <jfs@debian.org> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. On Debian systems, a copy of the GNU General Public License may be found in /usr/share/common-licenses/GPL. debian-goodies December 19 2006 checkrestart(1)
All times are GMT -4. The time now is 03:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy