- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- pseudo terminal
Operating System - HP-UX
1820390
Members
3628
Online
109623
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
Discussions
Discussions
Discussions
Forums
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
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
тАО12-24-2001 10:12 PM
тАО12-24-2001 10:12 PM
Hi, Could anyone tell me that what's pseudo terminal? what's it for? why we need pseudo terminal in hp-ux? I want to understand its mechanism thoroughly.
Thanks in advance.
Thanks in advance.
Keep finding is the way.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-24-2001 10:31 PM
тАО12-24-2001 10:31 PM
Solution
In a Nutshell:
pseudo terminals are required by processes that need to establish a terminal session like telnet/rlogin as well as TSM and other applications.
The kernel parameter npty controls the number that can be in use at the same time, but insf installs these only based on the -n option.
Example:
To create the ptys, two methods can be used (after adjusting npty in the kernel):
cd /dev
insf -n 500 -d pty0
insf -n 500 -d pty1
Note that both commands are needed. Or, the following method can do this in two steps:
cd /dev
insf -n 500 -C pseudo
The second form includes all the pseudo drivers.
For more information check:
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90147/B2355-90147_top.html&con=/hpux/onlinedocs/B2355-90147/00/00/17-con.html&toc=/hpux/onlinedocs/B2355-90147/00/00/17-toc.html&searchterms=pseudo%7cterminals&queryid=20011224-223532
pseudo terminals are required by processes that need to establish a terminal session like telnet/rlogin as well as TSM and other applications.
The kernel parameter npty controls the number that can be in use at the same time, but insf installs these only based on the -n option.
Example:
To create the ptys, two methods can be used (after adjusting npty in the kernel):
cd /dev
insf -n 500 -d pty0
insf -n 500 -d pty1
Note that both commands are needed. Or, the following method can do this in two steps:
cd /dev
insf -n 500 -C pseudo
The second form includes all the pseudo drivers.
For more information check:
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90147/B2355-90147_top.html&con=/hpux/onlinedocs/B2355-90147/00/00/17-con.html&toc=/hpux/onlinedocs/B2355-90147/00/00/17-toc.html&searchterms=pseudo%7cterminals&queryid=20011224-223532
Little learning is dangerous!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-25-2001 01:09 AM
тАО12-25-2001 01:09 AM
Re: pseudo terminal
simply think that we need device file to communicate between user and system.
if we login from dump or serial terminal we get real terminal device file but if we login from telnet /rlogin this is not real then it is pseudo device file.
that all,
if we login from dump or serial terminal we get real terminal device file but if we login from telnet /rlogin this is not real then it is pseudo device file.
that all,
enjoy any little thing in my life
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-25-2001 05:25 PM
тАО12-25-2001 05:25 PM
Re: pseudo terminal
It helps to understand that Unix does not communicate with terminals at all. Now this may sound strange but the concept of logging in requires some method to begin communicating with the terminal (getty for serial devices and modems, pty or pseudo terminals for network connections).
A program (such as getty or telnetd) then calls the login program to validate the user (again, HP-UX is just processing device file and file system requests), and finally schedules a shell program for the user to type commands.
So in order for anyone to communicate with HP-UX, there must be some sort of connection program (called a daemon), and a method to accept terminal characters and perform HP-UX functions (typically a shell).
The pty device files serve as a funnel for inbound and outbound characters. A network connection is quite complex as there are thousands of possible message types and these must be directed to the appropriate daemon or program. So daemons such as telnetd or rlogind are scheduled by inetd and they use pty device files to keep the data streams under control.
Bill Hassell, sysadmin
A program (such as getty or telnetd) then calls the login program to validate the user (again, HP-UX is just processing device file and file system requests), and finally schedules a shell program for the user to type commands.
So in order for anyone to communicate with HP-UX, there must be some sort of connection program (called a daemon), and a method to accept terminal characters and perform HP-UX functions (typically a shell).
The pty device files serve as a funnel for inbound and outbound characters. A network connection is quite complex as there are thousands of possible message types and these must be directed to the appropriate daemon or program. So daemons such as telnetd or rlogind are scheduled by inetd and they use pty device files to keep the data streams under control.
Bill Hassell, sysadmin
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP