HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Automating the terminal type with NIS logins
Operating System - Linux
1830992
Members
2553
Online
110018
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
01-25-2011 01:41 PM
01-25-2011 01:41 PM
Automating the terminal type with NIS logins
Hi there --
I am running NIS in an environment that has HP-UX 11.11 64-bit running on a PA-RISC rp3400 server, with Fedora Core 2 32-bit running on intel workstations. All users use the tcsh shell by default in their profiles. If more information is needed please let me know.
Users who log into the domain via a terminal window on the workstations are prompted for the terminal type which is normally dtterm. I want to automate the process so users are not prompted to enter in the above information. My plan is to modify the global-cshrc file on the master NIS server. I had several questions concerning this:
1. Is it better to modify global-cshrc, or should this be done at the individual user directory?
2. What is the correct syntax to use in either case?
3. Will the changes made go into effect upon the next login, or do I need to push out the changes via the make command?
I am running NIS in an environment that has HP-UX 11.11 64-bit running on a PA-RISC rp3400 server, with Fedora Core 2 32-bit running on intel workstations. All users use the tcsh shell by default in their profiles. If more information is needed please let me know.
Users who log into the domain via a terminal window on the workstations are prompted for the terminal type which is normally dtterm. I want to automate the process so users are not prompted to enter in the above information. My plan is to modify the global-cshrc file on the master NIS server. I had several questions concerning this:
1. Is it better to modify global-cshrc, or should this be done at the individual user directory?
2. What is the correct syntax to use in either case?
3. Will the changes made go into effect upon the next login, or do I need to push out the changes via the make command?
A Journey In The Quest Of Knowledge
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2011 02:59 PM
01-27-2011 02:59 PM
Re: Automating the terminal type with NIS logins
I found the solution. I modified the user account's .login file to read as follows:
#set up the terminal
# eval `tset -s -Q -m ':?hp' `
stty erase "^H" kill "^U" intr "^C" eof "^D" susp "^Z" hupcl ixon ixoff tostop
# tabs
By disabling the eval and tabs lines, I was able to have the terminal window appear without prompting the user.
#set up the terminal
# eval `tset -s -Q -m ':?hp' `
stty erase "^H" kill "^U" intr "^C" eof "^D" susp "^Z" hupcl ixon ixoff tostop
# tabs
By disabling the eval and tabs lines, I was able to have the terminal window appear without prompting the user.
A Journey In The Quest Of Knowledge
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