Update: Moved hedges from comments to here to aid in reading. This set of comments is entirely from my memory of *nix variants I have used and working through similar problems. There may be other / newer versions of *nix and ps that differ from my memory.
PS does not display the part of the command line after a pipe or redirect symbol, because it is not a part of the process - it is only a method of setting up the file descriptors in whatever program is calling the programs. The information after the redirection or pipe is another process or file, and would not be stored or shown in the process table.
The command foo | bar > biz would be parsed so that foo's STDOUT would be hooked up to bar's STDIN, and bar's STDOUT would be attached to the file handle attached to the file biz. Two different processes. Unless the shell (the one spawning the foo | ... commands) rewrites its $0 to reflect what is currently being written (which may be the case), the entire tubing between programs is not displayed using the ps command.
Now, that being said, I would like to be proven wrong, because there are a number of instances where that would be quite useful. :-)
--MidLifeXis
In reply to Re^2: How to know STDOUT associated with a process pid
by MidLifeXis
in thread How to know STDOUT associated with a process pid
by bgupta
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |