Hacktopia

Solaris’s version of top is called prstat /usr/bin/prstat

Example output

PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
15934 root 2208K 1680K sleep 10 0 0:00:41 12% tar/1
15933 root 1552K 1392K sleep 54 0 0:00:10 3.5% tar/1
15951 ch132182 3376K 3128K cpu0 59 0 0:00:00 0.1% prstat/1
753 noaccess 211M 126M sleep 59 0 0:36:31 0.0% java/35
15938 ch132182 8480K 3104K sleep 59 0 0:00:00 0.0% sshd/1
337 root 2328K 1560K sleep 100 - 0:02:52 0.0% xntpd/1
147 root 3920K 3104K sleep 59 0 0:04:03 0.0% picld/6
158 root 4576K 3896K sleep 59 0 0:02:15 0.0% nscd/26
166 root 2520K 1416K sleep 59 0 0:00:00 0.0% powerd/3
225 daemon 2832K 1808K sleep 59 0 0:00:00 0.0% rpcbind/1
258 daemon 2416K 1784K sleep 60 -20 0:00:00 0.0% lockd/2
235 root 2560K 1896K sleep 59 0 0:00:00 0.0% keyserv/4
237 root 2360K 1680K sleep 59 0 0:00:00 0.0% ypbind/1
153 daemon 4720K 2760K sleep 59 0 0:00:01 0.0% kcfd/5
15809 ch132182 3472K 2144K sleep 59 0 0:00:09 0.0% sftp-server/1
236 daemon 2712K 2088K sleep 59 0 0:00:00 0.0% statd/1
114 root 2520K 1664K sleep 59 0 0:00:11 0.0% snmpdx/1
65 root 9472K 6856K sleep 59 0 0:41:43 0.0% snmpd/1
257 root 2288K 1528K sleep 59 0 0:00:01 0.0% ttymon/1
Total: 75 processes, 237 lwps, load averages: 0.33, 0.25, 0.15

 Ever wonder what those codes mean when you are applying a solaris patch cluster

With regular programs a 0 is good and a 1 is bad.  Same basic theory, but you get diffrent error codes for diffrent reasons.  Most of the time you will get a 0 when the package is patch/upgraded and a 1 when you don’t even have the package, or it is already at the same level.  So a 1 is not as bad as it sounds.

Exit code     Meaning
0     No error
1     Usage error
2     Attempt to apply a patch that’s already been applied
3     Effective UID is not root
4     Attempt to save original files failed
5     pkgadd failed
6     Patch is obsoleted
7     Invalid package directory
8     Attempting to patch a package that is not installed
9     Cannot access /usr/sbin/pkgadd (client problem)
10     Package validation errors
11     Error adding patch to root template
12     Patch script terminated due to signal
13     Symbolic link included in patch
14     NOT USED
15     The prepatch script had a return code other than 0.
16     The postpatch script had a return code other than 0.
17     Mismatch of the -d option between a previous patch install and the current one.
18     Not enough space in the file systems that are targets of the patch.
19     $SOFTINFO/INST_RELEASE file not found
20     A direct instance patch was required but not found
21     The required patches have not been installed on the manager
22     A progressive instance patch was required but not found
23     A restricted patch is already applied to the package
24     An incompatible patch is applied
25     A required patch is not applied
26     The user specified backout data can’t be found
27     The relative directory supplied can’t be found
28     A pkginfo file is corrupt or missing
29     Bad patch ID format
30     Dryrun failure(s)
31     Path given for -C option is invalid
32     Must be running Solaris 2.6 or greater
33     Bad formatted patch file or patch file not found
34     The appropriate kernel jumbo patch needs to be installed