Re: tty5 respawning too fast - disabled
- To: firstname.lastname@example.org
- Subject: Re: tty5 respawning too fast - disabled
- From: John Patton <email@example.com>
- Date: Mon, 2 Apr 2001 13:40:18 -0500
- Message-id: <20010402134018.A18340@debian>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <01c601c0bb98$679c1800$b32d18d0@seele>; from email@example.com on Mon, Apr 02, 2001 at 12:14:41PM -0500
- References: <01c601c0bb98$679c1800$b32d18d0@seele>
I'm not sure why it happens exactly, but there is an easy
fix for it. As root, edit /etc/inittab. Towards the bottom
there will be a bunch of lines that look like the following:
1:2345:respawn:/sbin/getty -L 38400 tty1
2:23:respawn:/sbin/getty -L 38400 tty2
3:23:respawn:/sbin/getty -L 38400 tty3
4:23:respawn:/sbin/getty -L 38400 tty4
5:23:respawn:/sbin/getty -L 38400 tty5
6:23:respawn:/sbin/getty -L 38400 tty6
You will want to add the -L switch to each one. That option
disables carrier-detection, which is responsible for the
problems. You don't need carrier detection anyway unless you
are connecting to your box via a dumb terminal from a remote
location (you almost certainly aren't).
On Mon, Apr 02, 2001 at 12:14:41PM -0500, Jason Pepas wrote:
> lately i have been having a problem where the console reports "INIT: ID5 is respawing to often and will be disabled for 5 minutes"
> ID5 i figured out is tty5, because I cannot access it when this happens (at first I thoguht it meant PID 5, which was kswapd).
> I remember reading that certain processes are respawned by init when they get killed, and your terminals (tty's) are one such process
> but what could be killing it like that and causing it to respawn?
John Patton firstname.lastname@example.org
Get my GnuPG public key: finger email@example.com
"As long as people will accept crap, it will be financially
profitable to dispense it." - Dick Cavett