As a technology enthusiast and a middleware system administrator, over the years I observed many engineers working close to systems and noticed one peculiar feature about all of them, the all use ps and ls regardless of the reason they logged into the system, which is good. Talking more specifically about "ps", let me tell that it has come with variants from many technology groups over the two decades. The basic process detail command itself is not consistent over Unix and Linux implementations. Considering Solaris and RHEL as Ginny Pigs,
Process Detail : there are a lot of concerns regarding he listing of process detail over an operating system. For example, who can see the process details and who can not. Linux implementations (eg. RHEL) are not much fussy about this and they like to expose process details to all users. However, Solaris is a bit personality conscious, it makes sure that it shows the complete process details to either the user who owns the process or the "root".
- On a RHEL or any Linux implementation, ps -ef or ps auwwwx shows you all detail about every process currently running on that system.
- On Solaris systems, we use /usr/ucb/ps -auwwwx, to list the process details.
/usr/ucb/ps -auwwwx | grep [a]bcd.
Rising above the politics of ps, Unix and its variants have given us a wonderful command to deal with the issues we faced above. The "pgrep command"
This command was specifically designed to perform intelligent grep over the process listing internally. So to just see a detail listing of process we use,
pgrep -fl (full listing).
However you have to remember, on Solaris, you to be either root or process owner to be able to see the full listing of process details.
To view the process details of a specific user, we use something like,
pgrep -fl -u <username>.