HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- lshw output - odd strings displayed
Operating System - Linux
1826102
Members
4980
Online
109690
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
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
Go to solution
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
09-20-2007 04:06 AM
09-20-2007 04:06 AM
I'm mainly an HP-UX person but am currently managing some HP Linux as well.
Using the lshw command, before the main output I see upper case character strings appearing my Putty window, that do not appear in the final output. If I redirect stdout to /dev/null I see them, so they're not on stdout. If I redirect stderr to /dev/null I don't, so they're not to /dev/tty. If I redirect stderr to a file, I don't see them and the file is empty.
What's going on (or does Linux do this sort of thing)?
David
Using the lshw command, before the main output I see upper case character strings appearing my Putty window, that do not appear in the final output. If I redirect stdout to /dev/null I see them, so they're not on stdout. If I redirect stderr to /dev/null I don't, so they're not to /dev/tty. If I redirect stderr to a file, I don't see them and the file is empty.
What's going on (or does Linux do this sort of thing)?
David
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2007 03:06 AM
09-21-2007 03:06 AM
Solution
Those strings are actually reporting which of the system features lshw is testing at the moment. It checks for "if (isatty(2))" and outputs those strings when stderr is a tty.
It seems like lshw was first created on a rather slow (or huge) system. They flash by far to quickly to read on my laptop. They could be helpful if lshw stalls at some point. They would tell you what subsystem was causing the stall.
You can actually see all of the output if you run lshw inside of a 'script' command to catch the output into a typescript file. Since this is linux instead of HP-UX you can also get the source to lshw and see the actual code that writes the messages. On the other hand, the lshw man page has nothing to say about the behavior. I suppose the author thought that the meaning of the output was self-evident. At a much slower pace it may have been that way.
It seems like lshw was first created on a rather slow (or huge) system. They flash by far to quickly to read on my laptop. They could be helpful if lshw stalls at some point. They would tell you what subsystem was causing the stall.
You can actually see all of the output if you run lshw inside of a 'script' command to catch the output into a typescript file. Since this is linux instead of HP-UX you can also get the source to lshw and see the actual code that writes the messages. On the other hand, the lshw man page has nothing to say about the behavior. I suppose the author thought that the meaning of the output was self-evident. At a much slower pace it may have been that way.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP