popularité : 7%
Voici, une liste de commandes utiles pour
processus sous SOLARIS.
- /usr/bin/pflags [ -r ] pid ...
- /usr/bin/pcred pid ...
- /usr/bin/pmap [ -rxlF ] pid ...
- /usr/bin/pldd [ -F ] pid ...
- /usr/bin/psig pid ...
- /usr/bin/pstack [ -F ] pid ...
- /usr/bin/pfiles [ -F ] pid ...
- /usr/bin/pwdx [ -F ] pid ...
- /usr/bin/pstop pid ...
- /usr/bin/prun pid ...
- /usr/bin/pwait [ -v ] pid ...
- /usr/bin/ptree [ -a ] [ pid ... ]
- /usr/bin/ptime command [ arg ... ]
|ptime||Time the command, like time(1), but using microstate accounting for reproducible precision. Unlike time(1), children of the command are not timed.|
|ptree||Print the process trees containing the specified pids or users, with child processes indented from their respective parent processes. An argument of all digits is taken to be a process-id, otherwise it is assumed to be a user login name. Default is all processes.|
|pwait||Wait for all of the specified processes to terminate.|
|prun||Set each process running (inverse of pstop).|
|pstop||Stop each process (PR_REQUESTED stop).|
|pwdx||Print the current working directory of each process.|
|pfiles||Report fstat(2) and fcntl(2) information for all open files in each process.|
|pstack||Print a hex+symbolic stack trace for each lwp in each process.|
|psig||List the signal actions of each process.|
|pldd||List the dynamic libraries linked into each process, including shared objects explicitly attached using dlopen(3DL). See also ldd(1).|
|pmap||Print the address space map of each process.|
|pcred||Print the credentials (effective, real, saved UIDs and GIDs) of each process.|
|pflags||Print the /proc tracing flags, the pending and held signals, and other /proc status information for each lwp in each process.|
following options are
only) If the
stopped, display its machine registers.
(pmap only) Print the
process’s reserved addresses.
x (pmap only)
l (pmap only) Print
unresolved dynamic linker map
a (ptree only) All ;
include children of process 0.
v (pwait only)
report terminations to standard output.
F Force ; grab the target process
even if another process has control.
These proc tools stop their
target processes while inspecting them and reporting
results : pfiles, pldd, pmap,
pstack. A process can do nothing
while it is stopped. Thus,
for example, if the X server is inspected
by one of these
proc tools running in a
window under the X server’s control,
the whole window
become deadlocked because the
proc tool would be attempting to
print its results to a window
that cannot be refreshed. Logging
in from from another
system using rlogin(1) and
offending proc tool
would clear up the deadlock in this
Caution should be exercised when
using the -F flag. Imposing
two controlling processes on
one victim process can lead
to chaos. Safety
assured only if the primary controlling
process, typically a debugger,
has stopped the victim process and the
process is doing nothing at the
moment of application of the
proc tool in question.
Some of the proc tools
be applied to
core files, as shown
by the synopsis above. A
core file is a snapshot of a
process’s state and is produced by the
kernel prior to terminating
a process with a
signal or by the gcore(1) utility.
Some of the proc tools may need
to derive the name of
executable corresponding to the
process which dumped core or the
names of shared libraries
associated with the process.
These files are needed, for
example, to provide symbol table
information for pstack(1). If
the proc tool in question is
unable to locate the
needed executable or shared library,
some symbol information will be
unavailable for display.
Similarly, if a core file
one operating system release
is examined on a different operating
system release, the
run-time link-editor debugging
interface (librtld_db) may not
be able to initialize. In
this case, symbol information <span
shared libraries will not be