- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: continuous getty error in syslog
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
10-11-2002 06:13 AM
10-11-2002 06:13 AM
continuous getty error in syslog
syslog: getty: cannot open "ttydnn". errno: 19 where nn is a numeric value.
Any ideas on this are appreciated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2002 06:16 AM
10-11-2002 06:16 AM
Re: continuous getty error in syslog
Try this:
1. Modify /etc/inittab by removing the getty entries running on ttys that are not being used.
2. init q
C.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2002 06:21 AM
10-11-2002 06:21 AM
Re: continuous getty error in syslog
Do a vi /etc/inittab ans check for the ttydnn , you can commnet out the same if the line is not being used , incase it is being used by some serial device the port amy have some problem . Also after you comment the line you need to a ps -aef | grep on the ttydnn and then kill any process assoiated with it
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2002 06:23 AM
10-11-2002 06:23 AM
Re: continuous getty error in syslog
You may be missing device nodes. If so, an insf command (insf -C tty) can be used to recreate them. Man insf for details. Hardware may also be bad or have been removed. You can edit /etc/inittab and change the offending entries from 'respawn' to 'off'. After editing inittab, you will need to issue an 'init q' command to cause a re-read on /etc/inittab.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2002 06:25 AM
10-11-2002 06:25 AM
Re: continuous getty error in syslog
ttp1:234:respawn:/usr/sbin/getty -h ttydnn 9600
Just remark that line out of /etc/inittab if thats the case. Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2002 07:24 AM
10-11-2002 07:24 AM
Re: continuous getty error in syslog
errno 19 is no such device (see /usr/include/sys/errno.h)
As others have stated this error is generally caused by having a getty setup in /etc/inittab for a non-existent port.
If you're seeing different values of nn then it suggests that someone has either removed a load of device files that they didn't think they needed. Alternatively someone has restored a previous inittab that did contain many gettys.
The fix is to either recreate the device files if you need them, or remove (or turn off) the getty lines from /etc/inittab and run init q.
regards,
Darren.