So
will give you every process (including those not in a terminal) in a user-readable output. As you are using --sort I assume you are using the GNU version of ps. Also you require to pull the PID of each process from this list so you don't need the user-friendly switch.
The following uses the SysV options to list all processes; sort them as you were in the original post; listing only the PID.
Andrew
How is it possible under UNIX to restrain the number of digits of the PID number?
For instance, we have a product that generates a PID of 7 digits, and we would like to have only 6 digits maximum instead for the PID.
Thank you for your help. (1 Reply)
Hi,
I am working on HP-UX Release 11i.
I want to find the process id (PID) of the process running on a particular port.
lsof command fuser does not work on this system.
Please suggest some alternative.
Thanks (6 Replies)
Hello,
On a AIX 5.3.5.0 server, we have PID exceeding 999999. This cause some troubles in our programms.
I would like to know the process creation rules on aix :
- what is the maximum pid number ?
- what is the wrap limit on aix, and where to find it, how to configure pid wrap limit ?
-... (3 Replies)
Hello guys,
How to shut down a port number in AIX.
May be first I need to find out what is the process ID of that process that listens to this particular port.. Is there any command to find a process ID from the port number other than "lsof".
thanks (1 Reply)
Hi, is there a command that takes the PID of a process and that only diplays it's ni number?
I`m pretty sure it would require pipes but I tried a few things that ended up miserably...
Since the ps command doesn't show the ni unless I do ps -o ni but then I can't find a way to search the right... (2 Replies)
I want to sort a file with a list of words, in order of most occuring words to least occurring words as well as alphabetically.
ex:
file1:
cat 3
cat 7
cat 1
dog 3
dog 5
dog 9
dog 1
ape 4
ape 2
I want the outcome to be:
file1.sorted:
dog 1 (12 Replies)
Hi,
When I sum the RSS number in the ps command for a specific user and compare it with the RSS values of the prstat command of the same user - there is a big difference.
Server details: Solaris 10 5/09 s10s_u7wos_08 SPARC
prstat output:
NPROC USERNAME SWAP RSS MEMORY TIME ... (2 Replies)
This question is asked in an interview today that I have to return output with each PID number and the count of each PID number logged today. Here is the script that I have written. Can you confirm if that would work or not. The interviewer didn't said if my answer is correct or not. Can someone... (5 Replies)
Discussion started by: Subodh Kumar
5 Replies
LEARN ABOUT OSX
shlock
SHLOCK(1) BSD General Commands Manual SHLOCK(1)NAME
shlock -- create or verify a lock file for shell scripts
SYNOPSIS
shlock [-du] [-p PID] -f lockfile
DESCRIPTION
The shlock command can create or verify a lock file on behalf of a shell or other script program. When it attempts to create a lock file, if
one already exists, shlock verifies that it is or is not valid. If valid, shlock will exit with a non-zero exit code. If invalid, shlock
will remove the lock file, and create a new one.
shlock uses the link(2) system call to make the final target lock file, which is an atomic operation (i.e. "dot locking", so named for this
mechanism's original use for locking system mailboxes). It puts the process ID ("PID") from the command line into the requested lock file.
shlock verifies that an extant lock file is still valid by using kill(2) with a zero signal to check for the existence of the process that
holds the lock.
The -d option causes shlock to be verbose about what it is doing.
The -f argument with lockfile is always required.
The -p option with PID is given when the program is to create a lock file; when absent, shlock will simply check for the validity of the lock
file.
The -u option causes shlock to read and write the PID as a binary pid_t, instead of as ASCII, to be compatible with the locks created by
UUCP.
EXIT STATUS
A zero exit code indicates a valid lock file.
EXAMPLES
BOURNE SHELL
#!/bin/sh
lckfile=/tmp/foo.lock
if shlock -f ${lckfile} -p $$
then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
fi
C SHELL
#!/bin/csh -f
set lckfile=/tmp/foo.lock
shlock -f ${lckfile} -p $$
if ($status == 0) then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
endif
The examples assume that the file system where the lock file is to be created is writable by the user, and has space available.
HISTORY
shlock was written for the first Network News Transfer Protocol (NNTP) software distribution, released in March 1986. The algorithm was sug-
gested by Peter Honeyman, from work he did on HoneyDanBer UUCP.
AUTHORS
Erik E. Fair <fair@clock.org>
BUGS
Does not work on NFS or other network file system on different systems because the disparate systems have disjoint PID spaces.
Cannot handle the case where a lock file was not deleted, the process that created it has exited, and the system has created a new process
with the same PID as in the dead lock file. The lock file will appear to be valid even though the process is unrelated to the one that cre-
ated the lock in the first place. Always remove your lock files after you're done.
BSD June 29, 1997 BSD