Help me in finding process name and argument list without using pstat()

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Specifying a list name as argument and using that list in script.

Is there a way I can specify the name of a list as an argument to a shell script and then use the values of that list name in the script? I need to do this WITHOUT using case statements. Something like this: check.sh list1 #!/bin/bash list1="www.amazon.com www.google.com"...

2. Shell Programming and Scripting

Argument list too long

Hi Team, Here's the situation. I have approximately 300000 to 500000 jpg files in /appl/abcd/work_dir mv /appl/abcd/work_dir /appl/abcd/process_dir The above move command will work if the jpg files count is close to 50000 (not sure). If the count is less this mv command holds good. But if...

3. Shell Programming and Scripting

Argument list too long!!

Dear Experts, I have a list of 10K files in a directory. I am not able to execute any commands lile ls -lrt, awk, sed, mv, etc........ I wanna execute below command and get the output. How can I achieve it?? Pls help. root# awk -F'|' '$1 == 1' file_20120710* | wc -l /bin/awk: Argument list...

4. Shell Programming and Scripting

Finding process which ended another process

Hello, The scenario is as follows, I have a background process running initially for which i know the PID on machine1. I use ssh from machine 2 to execute a script in machine 1. For some reason the back ground process is terminated. I would like to know which process caused the...

5. UNIX for Advanced & Expert Users

Finding process id of subsequent process

hi all, I am trying to find the process id of the subsequent process created via fork and exec calls in perl. For eg: envVarSetter dataCruncher.exe < input.txt > output.txt When I fork and exec the above command, it returns only the pid of envVarSetter and I don't know how to find the...

6. Shell Programming and Scripting

finding * in command line argument

I have to write a script to determine whether given command line argument ($1) contains "*" symbol or not, if $1 does not contains "*" symbol add it to $1, otherwise show message "Symbol is not required". For e.g. If we called this script q5 then after giving , $ q5 /bin Here $1 is /bin, it...

7. Shell Programming and Scripting

Finding the process id of the process using the ports

Hi Any idea how to get the process id of the process using the ports lsof -i :portnumber does not work in my machine. I am on sun Solaris SPARC. Any suggestion is highly appreciated

8. Linux

Need help in finding process

Hello, Iam running a apache webserver in CentOS recenlty a hacker has attacked my server using RFI attack and did something in my server.. After that everyday at 8Pm my httpd is using about 5000 pid's actually in normal it takes only about 30 - 40 pid's. and also exim uses 2000 pid's totally my...

9. HP-UX

get CPU speed use pstat APIs

I get my CPU speed use pstat APIs use this program serach google and just test it #include <errno.h> #include <stdio.h> #include <unistd.h> #include <sys/param.h> #include <sys/pstat.h> #define CPU_ID 0 #define HZ_PER_MHZ 1000000 int main() { struct pst_processor pst; union pstun pu; ...

10. UNIX for Dummies Questions & Answers

finding process id

is there a way to find the process id of a process because i have same process invoked several times. when i need to kill them, i get confused with the id. Thanks, sskb :(

LEARN ABOUT FREEBSD

fuser

FUSER(1)						    BSD General Commands Manual 						  FUSER(1)

NAME

     fuser -- list IDs of all processes that have one or more files open

SYNOPSIS

     fuser [-cfkmu] [-M core] [-N system] [-s signal] file ...

DESCRIPTION

     The fuser utility writes to stdout the PIDs of processes that have one or more named files open.  For block and character special devices,
     all processes using files on that device are listed.  A file is considered open by a process if it was explicitly opened, is the working
     directory, root directory, jail root directory, active executable text, kernel trace file or the controlling terminal of the process.  If -m
     option is specified, the fuser utility will also look through mmapped files.

     The following options are available:

     -c      Treat files as mount point and report on any files open in the file system.

     -f      The report must be only for named files.

     -k      Send signal to reported processes (SIGKILL by default).

     -m      Search through mmapped files too.

     -u      Write the user name associated with each process to stderr.

     -M      Extract values associated with the name list from the specified core instead of the default /dev/kmem.

     -N      Extract the name list from the specified system instead of the default, which is the kernel image the system has booted from.

     -s      Use given signal name instead of default SIGKILL.

     The following symbols, written to stderr will indicate how files is used:

     r	    The file is the root directory of the process.

     c	    The file is the current workdir directory of the process.

     j	    The file is the jail-root of the process.

     t	    The file is the kernel tracing file for the process.

     x	    The file is executable text of the process.

     y	    The process use this file as its controlling tty.

     m	    The file is mmapped.

     w	    The file is open for writing.

     a	    The file is open as append only (O_APPEND was specified).

     d	    The process bypasses fs cache while writing to this file (O_DIRECT was specified).

     s	    Shared lock is hold.

     e	    Exclusive lock is hold.

EXIT STATUS

     The fuser utility returns 0 on successful completion and >0 otherwise.

EXAMPLES

     The command: ``fuser -fu .'' writes to standard output the process IDs of processes that are using the current directory and writes to stderr
     an indication of how those processes are using the directory and user names associated with the processes that are using this directory.

SEE ALSO

     fstat(1), ps(1), systat(1), iostat(8), pstat(8), vmstat(8)

STANDARDS

     The fuser utility is expected to conform to IEEE Std 1003.1-2004 (``POSIX.1'').

HISTORY

     The fuser utility appeared in FreeBSD 9.0.

AUTHORS

     The fuser utility and this manual page was written by Stanislav Sedov <stas@FreeBSD.org>.

BUGS

     Since fuser takes a snapshot of the system, it is only correct for a very short period of time.  When working via kvm(3) interface the report
     will be limited to filesystems the fuser utility knows about (currently only cd9660, devfs, nfs, ntfs, nwfs, udf, ufs and zfs).

BSD
								   May 13, 2011 							       BSD

HP-UX