Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!ICAEN.UIOWA.EDU!dbfunk
From: dbfunk@ICAEN.UIOWA.EDU (David B Funk)
Newsgroups: comp.sys.apollo
Subject: Re: Runaway inits
Message-ID: <9103290950.AA06856@icaen.uiowa.edu>
Date: 29 Mar 91 09:43:28 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Iowa Computer Aided Engineering Network, University of Iowa
Lines: 59

In posting <1991Mar28.165338.14067@midway.uchicago.edu> raymond thomas pierrehumbert writes:


> I definitely have the runaway init problem, but it seems to be 
> of a different flavor from that previously reported.  My /etc/ttys
> file has no spuriously "on" lines (Nothing is attached to any
> of the serial ports, and they are all "off" so far as I can see>
> 
> My process list and my /etc/ttys file follows.  Anybody notice
> anything?  Notice that I seem to have TWO init processes running,
> which is strange.  Notice also that the inits have grown to
> 23MB (after about 24 hours).  
[ stuff deleted ]
> % more /etc/ttys
> #
> # ttys - terminal initialization data
> #
> #device getty/program           term    on/off  other flags     comment
> 
> console "/etc/dm_or_spm"        apollo  on      secure          # use mkcon to r
> edirect console output
> display none                    apollo  off     secure          # DM pad devices
> tty01   none                    dumb    off     secure
> tty02   none                    dumb    off     secure
> tty03   none                    dumb    off     secure
> ttyp0   none                    dumb    on      secure
> ttyp1   none                    dumb    on      secure
> ttyp2   none                    dumb    on      secure
> ttyp3   none                    dumb    on      secure
> ttyp4   none                    dumb    on      secure

Raymond, your "ttys" file is causing your problem. Do NOT turn "on"
ports enabled for telnet/rlogin (the "ttyp?" things). These are
managed by "/etc/inetd" and not "/etc/init". When you turn them
"on" you have both "init" and "inetd" fighting over them, thus the
runaway init problem. The only reason for putting "ttyp?" pseudo-ttys
in your "ttys" file is to flag them as "secure". Otherwise leave them
out and just let inetd take care of them. Here's what you want your
ttys file to look like:

 % more /etc/ttys
 #
 # ttys - terminal initialization data
 #
 #device getty/program           term    on/off  other flags     comment
 
 console "/etc/dm_or_spm"        apollo  on      secure          # use mkcon to r
 edirect console output
 display none                    apollo  off     secure          # DM pad devices
 tty01   none                    dumb    off     secure
 tty02   none                    dumb    off     secure
 tty03   none                    dumb    off     secure
 ttyp0   none                    dumb    off     secure
 ttyp1   none                    dumb    off     secure
 ttyp2   none                    dumb    off     secure
 ttyp3   none                    dumb    off     secure
 ttyp4   none                    dumb    off     secure

Dave Funk