rds95@leah.Albany.Edu (Robert Seals) (07/28/89)
Hello, Every once in a while, my system does this strange thing where getty starts taking mucho cpu cycles. For example, right now there are 2 gettys taking up 90% of the machine cycles. All the other gettys look normal, i.e., they're just sitting asleep. Killing the offenders just spawns a couple new ones, of course; if I turn the offending lines off in /etc/ttys and then kill the processes, they still come back. Does anybody have any clues as to why and/or how to get rid of em? It's Ultrix 1.2 on a uVax II. anks, rob
debra@alice.UUCP (Paul De Bra) (07/29/89)
In article <1923@leah.Albany.Edu> rds95@leah.Albany.Edu (Robert Seals) writes: >...For example, right now there >are 2 gettys taking up 90% of the machine cycles. All the other gettys >look normal, i.e., they're just sitting asleep. Killing the offenders >just spawns a couple new ones, of course; if I turn the offending >lines off in /etc/ttys and then kill the processes, they still come back. >... You have to turn off the lines in /etc/ttys and then do a "kill -1 1". This tells init to not kill the gettys and not spawn any new ones. On some versions of Unix init "forgets" to kill the gettys so you might have to kill them by hand if you happen to have such a bogus version. Of course you then still have to find the cause of the looping gettys. Most likely there is a loose cable or broken serial interface. Paul. -- ------------------------------------------------------ |debra@research.att.com | uunet!research!debra | ------------------------------------------------------
bzs@bu-cs.BU.EDU (Barry Shein) (07/30/89)
>Every once in a while, my system does this strange thing where >getty starts taking mucho cpu cycles. For example, right now there >are 2 gettys taking up 90% of the machine cycles. All the other gettys >look normal, i.e., they're just sitting asleep. Killing the offenders >just spawns a couple new ones, of course; if I turn the offending >lines off in /etc/ttys and then kill the processes, they still come back. Almost certainly a hardware setup problem, getty thinks someone is coming in on the line and then changing its mind (or thereabouts.) One strong possibility is a very noisy terminal line or a grounding problem somewhere so garbage keeps coming in. It's possible you have modem control enabled on the lines in question but don't have the modem lines wired properly, either shut off modem control or re-wire the lines, particularly dtr, cd and rts/cts, these might be going up and down randomly (you don't say what kind of board this is.) If none of this helps or makes sense in your situation I'd diag the hardware itself, it could be a bad board tho that's less likely than the type of thing I mentioned above. Even if it worked yesterday a line could develop noisiness or grounding problems if it was marginal to begin with (did someone just install a large freezer unit near one of your terminal line runs? etc.) This sort of problem is often the wages of past (rs232) sins, and usually easy to fix once you get a handle on it. -- -Barry Shein Software Tool & Die, Purveyors to the Trade 1330 Beacon Street, Brookline, MA 02146, (617) 739-0202 Internet: bzs@skuld.std.com UUCP: encore!xylogics!skuld!bzs or uunet!skuld!bzs