01-30-2008
Problem to track process IDs in HP-UX machine
Hello All,
I need to track the exact process ID related to a particular application running on HP-UX machine. i.e. the exact functionality of fuser unix command.
fuser application.log // It gives the exact process ID for application.log
Since there is no provision for 'fuser' in HP-UX machine, please help me how I can achieve the same functionality.
Thanks & Regards
Abhishek
10 More Discussions You Might Find Interesting
1. Programming
Hello,
Can some one tell how to read the thread IDs of the current process in Sun Solaris.
Any help will be appreciated.
regards,
Murali (0 Replies)
Discussion started by: hmurali
0 Replies
2. Shell Programming and Scripting
Hi,
I am using sftp in my bash script.
I wanted to know whether if there is any way that we can track whether sftp has been successful or not..
Does sftp return any codes?
Thanks in adv (9 Replies)
Discussion started by: borncrazy
9 Replies
3. Shell Programming and Scripting
Hi all,
I need a script that will loop around all the current processes and take a pmap -x <process id> and output each pmap to a separate file.
Would anyone have a quick command to do this? (2 Replies)
Discussion started by: borderblaster
2 Replies
4. Shell Programming and Scripting
Hello,
I am trying to write a script that turns off the screensaver for a certain period of time, then come back on. I have had it up and running for a while, but then I decided to refactor it a bit for my family members that are less computer savvy.
I am starting a subshell for the "meat" of... (4 Replies)
Discussion started by: Narnie
4 Replies
5. UNIX for Dummies Questions & Answers
Hello all:
Working on a job I was asked get a simple script to perform the following task and would like to ask for some help. I'm looking forward to learning more and diving deeper into the World of Open Source servers.
I need a script for a Unix server, using as few lines as possible, that... (4 Replies)
Discussion started by: moahten
4 Replies
6. Shell Programming and Scripting
hi,
I have a job that spawns multiple child processes in background.. Catch is i want to wait for some jobs to finish before i spawn more background processes. (each job creates a file and deletes at the end of it . so i don't want start new jobs after x amount of disk size is used up)
now,... (2 Replies)
Discussion started by: ak_saravanan
2 Replies
7. Shell Programming and Scripting
Please help me with this question
I have a tantan.sh under /home/mydir which is a caller to another script "tantan.sh" under /home/anotherdir
-----------------------------------------------------------
/home/mydir/tantan.sh
------------------------------------------------------------... (6 Replies)
Discussion started by: guruincredible
6 Replies
8. Shell Programming and Scripting
Hi,
I have four tomcat instances named PNK, PNK1, PNK2, PNK3.
All are running on the same server.
To kill tomcat instance I usually do below for PNK1,PNK2,PNK3
kill -9 `ps -ef|grep tomcat|grep PNK1|grep -v grep|awk '{print $2}'`
But the above command does not work for PNK. Can some... (7 Replies)
Discussion started by: lpprasad321
7 Replies
9. Shell Programming and Scripting
Hi,
I need to list out the processes which are started/restarted today in my Solaris box. If not possible need to convert the process uptime in minutes or seconds and compare it with a configurable value to list out those process ids for further processing in my scripting.
Can any one guide... (7 Replies)
Discussion started by: ananan
7 Replies
10. UNIX for Beginners Questions & Answers
I will initiate a process from Server1 and the flow is as follow
Server1 --> Web server --> Application server --> DB Server
Note all seperate unix servers.
Now I need to put a trace for that process to track the timings from each server.
Like the below trace should be there:
... (5 Replies)
Discussion started by: saraperu
5 Replies
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