GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- the command ps and how to get all the flags thrown...
Operating System - HP-UX
1845895
Members
4849
Online
110250
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
10-31-2000 02:13 PM
10-31-2000 02:13 PM
the command ps and how to get all the flags thrown to it
In solaris I can use /usr/ucb/ps auxww and I will be able to see all the flags that were thrown to a process when it was called. Is there a similar way to do that in HP? The processes I'm talking about receive about 5 lines of text, so using the xpg4 version and reordering the data isn't feasible.
Thanks,
Dan
Thanks,
Dan
Everything's simple until you try and do it.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2000 03:50 PM
10-31-2000 03:50 PM
Re: the command ps and how to get all the flags thrown to it
Daniel:
This has come up several times lately. Unfortunately, only a subset of the whole command string is saved by 'ps'. An old document (#1653012245) notes that "the pstat kernel code data structures were modified in 8.0 and the command string length was reduced to 60 characters. There is no standard for this length...[and] this length
should not be relied on in future releases."
This is consistent with the man pages for ps which also note: "Users of ps must not rely on the exact field widths and spacing of its output, as these will vary depending on the system, the release of HP-UX, and the data to be displayed."
...JRF...
This has come up several times lately. Unfortunately, only a subset of the whole command string is saved by 'ps'. An old document (#1653012245) notes that "the pstat kernel code data structures were modified in 8.0 and the command string length was reduced to 60 characters. There is no standard for this length...[and] this length
should not be relied on in future releases."
This is consistent with the man pages for ps which also note: "Users of ps must not rely on the exact field widths and spacing of its output, as these will vary depending on the system, the release of HP-UX, and the data to be displayed."
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2000 07:12 AM
11-01-2000 07:12 AM
Re: the command ps and how to get all the flags thrown to it
Unfortunately, James is right. It is one of the things I would like to see changed in future HP releases, but I am not holding my breath.
The best workaround I know is to replace the binary/script in quesion with a wrapper which calls your program while recording the flags & PID in a logfile.
The best workaround I know is to replace the binary/script in quesion with a wrapper which calls your program while recording the flags & PID in a logfile.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP