Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!cbosgd!mandrill!neoucom!wtm From: wtm@neoucom.UUCP (Bill Mayhew) Newsgroups: comp.sys.att Subject: Re: Adding extra console window gettys: maybe not a good idea Message-ID: <755@neoucom.UUCP> Date: Mon, 16-Nov-87 08:54:54 EST Article-I.D.: neoucom.755 Posted: Mon Nov 16 08:54:54 1987 Date-Received: Thu, 19-Nov-87 20:07:28 EST References: <750@neoucom.UUCP> <162@manta.UUCP> Organization: Northeastern Ohio Universities College of Medicine Lines: 23 Summary: Various results <> I've had mixed results on this one. I got sevral letters to the effect, "I've been doing this for the last year, and never had a problem". I also received several letters to the effect, "I had the same results as you." Perhaps, this is a hardware difference? I forget what version of hardware gets displayed at the boot-up at the moment. I was playing it very cool and only had one extra console window. I got the error message when only one window was awake. It seems that when the getty respaws, it grabs new memory for the window, but doesn't free the previous memeory. What is odd is that this does not seem to happen with only one console window. Perhaps, this could be a problem in a shared library used for window management. It could be that oddness happens if the idle getty's memory gets swapped out. I'm not sure if this really happens; I've had too many other irons in the fire to get a chance to check this out. Diagnostics doesn't report anything out of the ordinary. -Bill