Return to ps.8 CVS log

Up to [Research Unix] / researchv10dc / dist / man / v3 / man8

Annotation of researchv10dc/dist/man/v3/man8/ps.8, revision 1.1

1.1     ! root        1: .pa 1
        !             2: .he 'PS (VIII)'1/20/73'PS (VIII)'
        !             3: .ti 0
        !             4: NAME           ps -- process status
        !             5: .sp
        !             6: .ti 0
        !             7: SYNOPSIS       /usr/adm/ps [ -xlt____ ]
        !             8: .sp
        !             9: .ti 0
        !            10: DESCRIPTION
        !            11: .br
        !            12: .in 8
        !            13: ps__
        !            14: prints certain facts about active
        !            15: processes.
        !            16: The information is columnar and consists of:
        !            17: 
        !            18: .in +3
        !            19: The (numerical) ID of the user associated
        !            20: with the process;
        !            21: 
        !            22: The last character of the control typewriter of the process
        !            23: or "x" if there is no control typewriter;
        !            24: "x" lines are suppressed unless the "x" option
        !            25: is given.
        !            26: 
        !            27: The number of 512-byte disk blocks holding the core
        !            28: image of the process;
        !            29: 
        !            30: The process's unique ID (only with "l" option)
        !            31: 
        !            32: The number of hours (mod 100) and minutes of system, disk, and
        !            33: user-process time accumulated by the process and
        !            34: all its terminated descendants (only with "t" option)
        !            35: 
        !            36: An educated guess as to the command line which caused the
        !            37: process to be created.
        !            38: 
        !            39: .in -3
        !            40: Some caveats:
        !            41: 
        !            42: The guess as to the command name and arguments is obtained by examining
        !            43: the process's stack.
        !            44: The process is entitled to destroy this information.
        !            45: Also, only processes whose core images are on disk have
        !            46: visible names.
        !            47: The ps__ command in particular
        !            48: does not, nor does any other process which happens to
        !            49: be in core at the same time.
        !            50: ps__ tries to overcome this limitation by spawning
        !            51: a subprocess designed to take up the other core
        !            52: slot, and is usually successful.
        !            53: Because ps__ examines a dynamically changing data structure,
        !            54: it can produce incorrect results, for example if
        !            55: a process's core image moves between the time
        !            56: ps__ gets its disk address and reads its stack.
        !            57: 
        !            58: Besides its utility for simple spying,
        !            59: ps__ is the only plausible
        !            60: way to find the process number of someone you are trying
        !            61: to kill (VIII).
        !            62: .sp
        !            63: .in 16
        !            64: .ti 0
        !            65: FILES          /dev/rf0,
        !            66: /sys/sys/unix (to get magic numbers).
        !            67: .sp
        !            68: .ti 0
        !            69: SEE ALSO       kill (VIII)
        !            70: .sp
        !            71: .ti 0
        !            72: DIAGNOSTICS    "Bad RF", if
        !            73: a bad swap address turns up;
        !            74: various missing-file diagnostics.
        !            75: .sp
        !            76: .ti 0
        !            77: BUGS           As described.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.