hi all, am a newbie to solaris and am using solaris 9 os. I wanted to know how to interpret the output from a truss command ?? my truss command was to trace a systems calls etc : /usr/bin/truss -p [pid] thanks in advance, cesar.

the output i get from the truss command looks like this : /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /8: poll(0xB4F7FD80, 0, 50) = 0 /59: lwp_cond_wait(0x01C38250, 0x01C38238, 0x00000000) (sleeping...) /60: lwp_cond_wait(0x01C382B8, 0x01C382A0, 0x00000000) (sleeping...) /58: lwp_cond_wait(0x01437348, 0x01437330, 0x00000000) (sleeping...) /71: lwp_cond_wait(0x02037070, 0x02037058, 0x00000000) (sleeping...) /72: lwp_mutex_lock(0x00037958) (sleeping...) /56: recvfrom(36, 0x02119CA0, 16384, 0, 0xADA7F0BC, 0xADA7F0DC) (sleeping...) /46: lwp_mutex_lock(0x000F0E38) (sleeping...) /35: lwp_mutex_lock(0x000F0EA8) (sleeping...) /86: lwp_mutex_lock(0x000F0EE0) (sleeping...) /53: lwp_mutex_lock(0x00037958) (sleeping...) /38: lwp_mutex_lock(0x000F0E38) (sleeping...)

My guess is it is doing little to nothing. What are you trying to learn or do? I read it wrong and answer it wrong too. So get off my case you peanut.

was trying to troubleshoot this application server which seemed to be in a hung state as the clients running on that app were taking ages to respond to command which normally takes split seconds.

Then I'd say it is correctly showing a problem if you have correctly used the command. You did put the correct ID in didn't you? Not sure where to look next. More diags needed and troubleshooting. Did it just happen or after some other fix or update? Any hardware changes? Run system diags, disable other services and or hardware. Consider reload as last ditch. I read it wrong and answer it wrong too. So get off my case you peanut.