init won't start my (m)getty process!

init won't start my (m)getty process!

Post by ASCII of Ameri » Fri, 02 Dec 1994 06:08:11



I have tried everything I know how to try.  I've tried agetty, getty,
getty_ps, and mgetty.  I've tried juggling the various configuration
files.  I've tried "kill -HUP 1", "init q", and "reboot."  I still
can't seem to get init to start my getty process!

Here's my inittab.  Note the "Dialup lines" section where I try to
spawn mgetty on three different ttyS* (I only really care about ttyS1,
but I wanted to be safe).

David Wuertele

#
# inittab       This file describes how the INIT process should set up
#               the system in a certain run-level.
#

#
# Author:       Miquel van Smoorenburg,

#
# Default runlevel.
id:5:initdefault:

# System initialization (runs when system booOWER IS BACK"

# If power comes back in single user mode, return to multi user mode.
ps:S:powerokwait:/sbin/init 5

# The getties in multi user mode on consoles an serial lines.
#
# NOTE NOTE NOTE adjust this to your getty or you will not be
#                able to login !!
#
# Note: for 'agetty' you use linespeed, line.
# for 'getty_ps' you use line, linespeed and also use 'gettydefs'
#c1:12345:respawn:/sbin/agetty 38400 tty1
#c2:12345:respawn:/sbin/agetty 38400 tty2
#c3:45:respawn:/sbin/agetty 38400 tty3
#c4:45:respawn:/sbin/agetty 38400 tty4
#c5:45:respawn:/sbin/agetty 38400 tty5
#c6:456:respawn:/sbin/agetty 38400 tty6

# Serial lines
#S1:456:respawn:/sbin/uugetty ttyS1 38400
#S2:456:respawn:/sbin/uugetty ttyS2 38400
#S3:456:respawn:/sbin/uugetty ttyS3 38400

# Dialup lines
#d1:45:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0
#d2:45:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1
d0:456:respawn:/usr/sbin/mgetty -m 7 ttyS0
d1:456:respawn:/usr/sbin/mgetty -m 7 ttyS1
d2:456:respawn:/usr/sbin/mgetty -m 7 ttyS2

# Runlevel 6 used to be for an X-window only system, until we
discovered
# that it throws init into a loop that keeps your load avg at least 1
all
# the time. Thus, there is now one getty opened on tty6. Hopefully no
one
# will notice. ;^)
# It might not be bad to have one text console anyway, in case
something
# happens to X.
x1:6:wait:/etc/rc.d/rc.6

# End of /etc/inittab

 
 
 

init won't start my (m)getty process!

Post by Klaus Lichtenwald » Fri, 02 Dec 1994 18:11:21



Quote:>Here's my inittab.  Note the "Dialup lines" section where I try to
>spawn mgetty on three different ttyS* (I only really care about ttyS1,
>but I wanted to be safe).
># Dialup lines
>#d1:45:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0
>#d2:45:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1
>d0:456:respawn:/usr/sbin/mgetty -m 7 ttyS0
>d1:456:respawn:/usr/sbin/mgetty -m 7 ttyS1
>d2:456:respawn:/usr/sbin/mgetty -m 7 ttyS2

I think you meant to say -x 7, -m defines an alternative/additive init
chat. I bet your modem wont answer to a '7', making mgetty think the connection
to the modem is lost ("interrupted system call").

Make that -x 7, and if you don't get it to work, send the initialisation
part from the logfile.

Klaus
--
__________________________________________________________________________
Klaus Lichtenwalder, Dipl. Inf., Buschingstr. 65
D-81677 Muenchen, F.R. Germany,  Fax +49-89-98292755


 
 
 

1. init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv0:

In my new job, I have inherited a FreeBSD Box. To physically check out
some hardware I performed a Shutdown (can't remember the exact arguments
used now).

At restart, kernel processing appears to proceed without problems, until
the system somewhere during init, it apparently can't find getty. A
typical error report line looks like:
Jan 16 23:58:13 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv0: No such file or directory
From this point, every 30 seconds the system constantly attempts to
execute getty.

And I can't get any response past this point. No keystrokes seem to do
anything, no tty devs of any kind seem to be in place. I can't RCMD from
another box anywhere.

I can reboot to a startup floppy (made with the boot.flp using fdimage),
but as the prblem seems to be a missing file (getty) I can;t get much
further.

I can get to the holographic tty4, but can't do much there either.

I can restart in single user mode, but that puts the system into
read-only mode and so I can't even see the /usr directory and files.

Any help appreciated......

2. Numbered environment variable in Bourne shell

3. getty won't start

4. breaking up large files into smaller pieces?

5. init: can't exec getty 'perl' for port /dev/cuaa0

6. RIP and PPP

7. init: can't exec getty 'none' ...

8. Alcatel speed touch usb

9. NFS-Root /sbin/init won't start

10. Root process won't start correctly form crontab in AIX 4.3.3

11. Processes Won't Start

12. help?: Re-installation of Vision 97 (processes won't start)

13. Root process won't start correctly form crontab in AIX 4.3.3