GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- telnetd, kernel params, creating device files
Operating System - HP-UX
1858262
Members
4179
Online
110386
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
back
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
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-05-2000 10:45 AM
12-05-2000 10:45 AM
Hello admins!
We are reaching the max telnet files avail for users and ocassionally getting connection errors and device file missing syslog msgs. I understand I need to modify the kernel and create additional device files to match the kernel param nstrtel.
Q: Do I need to increase the nstrpty and npty params inaddition to the nstrtel? All are set to the defaul of 60.
Q 2: What specific files do I create in /dev and when I look at the insf man pages it appears I use the insf -n or insf -s switches...correct? If so what is the insf -d device switch used for? (someone posted a previous response to a similar questin saying you can use SAM to create the device files, but I must be blind because I couldn't see where in SAM you can do this).
tia,
Doug
We are reaching the max telnet files avail for users and ocassionally getting connection errors and device file missing syslog msgs. I understand I need to modify the kernel and create additional device files to match the kernel param nstrtel.
Q: Do I need to increase the nstrpty and npty params inaddition to the nstrtel? All are set to the defaul of 60.
Q 2: What specific files do I create in /dev and when I look at the insf man pages it appears I use the insf -n or insf -s switches...correct? If so what is the insf -d device switch used for? (someone posted a previous response to a similar questin saying you can use SAM to create the device files, but I must be blind because I couldn't see where in SAM you can do this).
tia,
Doug
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2000 10:53 AM
12-05-2000 10:53 AM
Solution
Try this link in the technical knowledge base:
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=43c863d61903c7d024/screen=ckiDisplayDocument?docId=400000000202094
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=43c863d61903c7d024/screen=ckiDisplayDocument?docId=400000000202094
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2000 10:58 AM
12-05-2000 10:58 AM
Re: telnetd, kernel params, creating device files
Doug:
Document #A5733141 gives the following procedure for you:
1. insf -d pty -n 400 (for ptym and ptys pseudo drivers)
2. cd /stand
3. Execute the following commands:
insf -evd tlclts
insf -evd tlcotsod
insf -evd tlcots
insf -d tels
insf -d telm
4. Edit the system file to contain the following parameters:
npty 400
nstrpty 400
5. Execute the following command to build a new kernel:
mk_kernel -s system
6. Execute the following commands when you reboot the system:
mv /stand/vmunix /stand/vmunix_prev
cp /stand/vmunix_test /stand/vmunix
7. Install the following telnet patches:
PHNE_14957 telnetd(1M):cumulative:
PHNE_16546 panic:telnet:kernel:cumulative:
PHNE_18075 streams:cumulative:
PHNE_18554 XPORT:ARPA:Transport:
PHCO_18302 mksf(1M):lssf(1M):insf(1M):rmsf(1M
PHNE_14820 telnet:opost:flag:authentication:
PHNE_14976 UTF8:STREAMS:PTY:line:discipline:support
The patches are for 11.0. As always, check for superceded ones.
...JRF...
Document #A5733141 gives the following procedure for you:
1. insf -d pty -n 400 (for ptym and ptys pseudo drivers)
2. cd /stand
3. Execute the following commands:
insf -evd tlclts
insf -evd tlcotsod
insf -evd tlcots
insf -d tels
insf -d telm
4. Edit the system file to contain the following parameters:
npty 400
nstrpty 400
5. Execute the following command to build a new kernel:
mk_kernel -s system
6. Execute the following commands when you reboot the system:
mv /stand/vmunix /stand/vmunix_prev
cp /stand/vmunix_test /stand/vmunix
7. Install the following telnet patches:
PHNE_14957 telnetd(1M):cumulative:
PHNE_16546 panic:telnet:kernel:cumulative:
PHNE_18075 streams:cumulative:
PHNE_18554 XPORT:ARPA:Transport:
PHCO_18302 mksf(1M):lssf(1M):insf(1M):rmsf(1M
PHNE_14820 telnet:opost:flag:authentication:
PHNE_14976 UTF8:STREAMS:PTY:line:discipline:support
The patches are for 11.0. As always, check for superceded ones.
...JRF...
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