HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Pseudo tty problems
Operating System - HP-UX
1834043
Members
2666
Online
110063
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
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
03-15-2002 11:18 AM
03-15-2002 11:18 AM
Pseudo tty problems
I am trying to port our application from linux/SCO to an HP-UX 10.20 system, and it makes use of pseudo terminals.
I can't get the slave to open when using /dev/ptmx, and when using /dev/ptyXX, when the slave closes, the master does not notice it and hangs.
On this particular system that I am using to port my app (which is the customer's system) is running HP-UX 10.20.
When I telnet into the system, it is using BSD style pseudo ttys (/dev/ttyp9, for example).
I've attached the relevant code.
...help!...
I can't get the slave to open when using /dev/ptmx, and when using /dev/ptyXX, when the slave closes, the master does not notice it and hangs.
On this particular system that I am using to port my app (which is the customer's system) is running HP-UX 10.20.
When I telnet into the system, it is using BSD style pseudo ttys (/dev/ttyp9, for example).
I've attached the relevant code.
...help!...
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2002 09:08 PM
03-15-2002 09:08 PM
Re: Pseudo tty problems
/dev/ptmx is associated with the STREAMS pts(7) driver. Check the man-pages pts(7) and ptm(7) for details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2002 07:55 AM
03-18-2002 07:55 AM
Re: Pseudo tty problems
I am familiar with the STREAMS pty system. The device /dev/ptmx is there but doesn't seem to work: When I try to open the slave the program blocks. So I switched to using BSD style ptys (which, by the terminal names I get, it seems telnetd is also using).
BSD style ptys almost work. If, after the slave is closed, I do a read, the master simply hangs, instead of returning 0 (EOF).
Obviously, since I can telnet into the system and don't seem to have any telnetds being stuck, there must be some method of being notified that the slave was closed.
So, I guess my real question is: How is the master side notified that the slave side has been closed?
BSD style ptys almost work. If, after the slave is closed, I do a read, the master simply hangs, instead of returning 0 (EOF).
Obviously, since I can telnet into the system and don't seem to have any telnetds being stuck, there must be some method of being notified that the slave was closed.
So, I guess my real question is: How is the master side notified that the slave side has been closed?
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 2025 Hewlett Packard Enterprise Development LP