I found the issue of top in Solaris for you. You need to do it twice to get the CPU state. That means the first output of top which missed the CPU state but it will appear in next cycle.
So the solution is:
top -s 1 -d 2 > top.out
Then you will see the CPU state.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.