/etc/getty and /etc/inittab woes

/etc/getty and /etc/inittab woes

Post by Chris Cheyn » Wed, 05 Jun 1991 05:57:40



I have a problem with AIX 3.1 and gettys.  I add a line for my custom
getty like this into /etc/inittab:
        tty2:2:respawn:/etc/mygetty -a tty2 19200

and all looks like it goes well.  I wander off and leave the port
alone for a while, perhaps with people trying to call into it, or not,
I'm not altogether certain, but I come back and am looking at this
line:
        tty2:2:respawn:/etc/getty /dev/tty2

which is not right for what I want.  No person has modified it that I
know of, so I'm assuming that some process is thwacking me.  Has anyone
else encountered this, and if so, how did you solve the problem?

This reset of /etc/inittab entries occurs always after a reboot and
occurs other times (these circumstances I'm not sure of).  Any
suggestions?

By the way, mygetty is a wrapper for a modem so I don't make it chatter
endlessly.  It forks off /etc/getty with the -r option.

Any suggestions for solving this problem (as well as explaining why
sometimes I receive a SIGCHLD signal) would be appreciated.

Thanks in advance.

chris
---
Chris Cheyney                              | When you go to North Carolina,
386 Rose Creek Road, Franklin NC 28734     | you set your watch back 20 years.

UUCP:     {backbones}!emory!rsiatl!chris   | your laws back 100.

 
 
 

/etc/getty and /etc/inittab woes

Post by Robin D. Wilso » Thu, 06 Jun 1991 00:59:30



writes:

Quote:> I have a problem with AIX 3.1 and gettys.  I add a line for my custom
> getty like this into /etc/inittab:
>    tty2:2:respawn:/etc/mygetty -a tty2 19200

This is not the best way to use something different than the default.  Use
SMIT to set the port to "Login:  DISABLED".  This will create an entry in the
inittab file that looks like this:

tty2:2:off:/etc/getty /dev/tty2

THEN... add an entry that looks like:

TTY2:2:respawn:/etc/mygetty -a tty2 19200

The fact that this entry is not contained in the ODM will prevent the
system from trying to "correct" it using the settings you defined through
SMIT.

Quote:> and all looks like it goes well.  I wander off and leave the port
> alone for a while, perhaps with people trying to call into it, or not,
> I'm not altogether certain, but I come back and am looking at this
> line:
>    tty2:2:respawn:/etc/getty /dev/tty2

This is what the ODM gets for you.  It will determine the "correct" settings  
for a tty based on what you set through SMIT.  If you set it up correctly in
SMIT, then you will get what you wanted here.

Quote:> which is not right for what I want.  No person has modified it that I
> know of, so I'm assuming that some process is thwacking me.  Has anyone
> else encountered this, and if so, how did you solve the problem?

The process that is "thwacking you" is probably SMIT.  Or, it could be anyone  
of a number of other process that call the syschck routines.

Quote:> By the way, mygetty is a wrapper for a modem so I don't make it chatter
> endlessly.  It forks off /etc/getty with the -r option.

I suggest you use "DELAY" for the "Enable LOGIN" field in SMIT.  This uses the  
"uugetty -r" code to keep the modem from "chattering".  If you like, you can  
mail me, and I will send you (via email) a complete guide to modem setup on the  
rs-6000.

Quote:> Any suggestions for solving this problem (as well as explaining why
> sometimes I receive a SIGCHLD signal) would be appreciated.

Don't know about this one...   When do you receive the SIGCHLD?

+-----------------------------------------------------------------------------+
|The views expressed herein, are the sole responsibility of the typist at hand|
+-----------------------------------------------------------------------------+
|UUCP:     pensoft!robin                                                      |
|USNail:   701 Canyon Bend Dr.                                                |
|          Pflugerville, TX  78660                                            |
|          Home: (512)251-6889      Work: (512)343-1111                       |
+-----------------------------------------------------------------------------+

 
 
 

1. login problems after tinkering with/etc/inittab & /etc/uugetty.

Hi!
Recently I tried to set up a my Linux1.23 (slackware) for incoming calls.
I did so, but after that my login system failed.
I can't login on to the computer except as a root.
it says:
dl_boot: open /dev/zero failed!

What does it mean?
Pavel
---
No SIGNATURE. Call (250) 595-7289 or visit my Web site at
http://www.islandnet.com/~skendall/pavel.htm for complete copy of my resume.
Avail. in: Word for Win 6.0 , WP 6.1 for win and Envoy Reader formats.
Pavel Zaitsev
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Don't get mad  -- get even.
  -- Kennedy's Dictionary.

2. Connect problems

3. CDE vs. /etc/passwd, /etc/shadow and /etc/group

4. Linux Resource

5. ssh chrooted enviroment WITHOUT /bin /etc /lib - etc etc in the users dir ?

6. Gateway video chipset/ Red Hat installation

7. 3.5 MO, zip, etc, etc, etc.

8. none

9. ps/1, Lilo, etc etc etc problems w/ instalation

10. Looking for sample /etc/named.conf and etc/resolv.conf and /etc/hosts

11. LINUX, 3COM ImpactIQ, ISDN, etc, etc, etc...

12. /etc/inittab problems

13. startx and /etc/inittab