- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Process behaviour
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 07:06 AM
07-15-2002 07:06 AM
Process behaviour
Is there any other commands available on UNIX other than TRUSS to find out the problem with a particular process or command?.
Thnaks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 08:58 AM
07-15-2002 08:58 AM
Re: Process behaviour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 11:39 AM
07-15-2002 11:39 AM
Re: Process behaviour
If required I can post the detailed procedure for this.-q4
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 11:41 AM
07-15-2002 11:41 AM
Re: Process behaviour
I have no clue about the q4, could you please post the procedure? any utilities?.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 12:00 PM
07-15-2002 12:00 PM
Re: Process behaviour
http://forums.itrc.hp.com/cm/QuestionAnswer/0,,0xc6abd5fab40ed6118ff40090279cd0f9,00.html
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 01:45 PM
07-15-2002 01:45 PM
Re: Process behaviour
Check the following.
Regards,
Use q4 to get a stack trace using the process ID number.
Note: q4 is available at HP-UX Version 10.10 and above. An example (using process id 21699):
# q4 /dev/mem /stand/vmunix
q4> load struct proc from proc max nproc; keep p_stat
loaded 1284 struct proc's as an array (stopped by max count)
kept 571 of 1284 struct proc's, discarded 713
q4> keep p_pid == 21699;trace pile
kept 1 of 571 struct proc's, discarded 570
stack trace for process at 0x843edc0 (pid 21699), thread at
0x8500300 (tid 28011)
process was not running on any processor
save+0x0
_swtch+0x138
real_sleep+0x330
_sleep_one+0x14
semop+0x71c
syscall+0x1a4
q4> quit
The above indicates that the process is sleeping after doing a semop call. The next step might be to see how this process is using semaphores or, if this is a system process, whether there are any known issues with this process sleeping on semop.
Steps to set up q4 on your system are as follows:
cd /usr/contrib/lib
uncompress Q4Lib.tar.Z:
tar -xvf Q4Lib.tar
cp /usr/contrib/lib/q4lib/sample.q4rc.pl ~/q4rc.pl
Change the following line in ~/q4rc.pl:
# push (INC, "/usr/local/lib/q4lib");
to
push (INC, "/usr/local/lib/q4lib");
Set up your PATH:
export PATH=$PATH:/usr/contrib/bin
Prep your kernel:
q4pxdb /stand/vmunix
Note: dde (requires DCE product) and analyze (10.01 and below) can also be used to look at a process's stack trace.
8. Public domain software such as trace can be used to trace a process's system calls. trace is available for download from the public domain software page located off of the www.software.hp.com Web site.
This software is particularly useful because it enables you to see what calls a process is making, if any, and whether the process is looping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 02:01 PM
07-15-2002 02:01 PM
Re: Process behaviour
You can also try tusc. You can find
it here :
http://hpux.cict.fr/hppd/hpux/Sysadmin/tusc-7.0/
Regards,
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2002 02:05 PM
07-15-2002 02:05 PM
Re: Process behaviour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2002 05:53 AM
07-16-2002 05:53 AM
Re: Process behaviour
For binaries you can try trace or adb, the absolute debugger.
HTH
mark