Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!rutgers!brl-adm!adm!swa@COMET.LCS.MIT.EDU From: swa@COMET.LCS.MIT.EDU (Steven Augart) Newsgroups: comp.unix.wizards Subject: console process getting killed Message-ID: <1566@brl-adm.ARPA> Date: Tue, 16-Dec-86 13:01:14 EST Article-I.D.: brl-adm.1566 Posted: Tue Dec 16 13:01:14 1986 Date-Received: Wed, 17-Dec-86 19:00:10 EST Sender: news@brl-adm.ARPA Lines: 27 From: Paul MarshDate: 9 Dec 86 01:08:59 GMT Any process associated with the console terminal was being terminated at random intervals. It puzzles me as to why this would problem would just startup the time it did. To the best of my knowledge, the only thing being done on a systems level, is that we were running the "/etc/netsetup" script, which modifies /etc/hosts, /etc/networks, and /etc/hosts.equiv files, for configuring a local area network. This may not be your answer, but I know (from bitter experience) that this problem happens on 4.2 BSD (and therefore on Ultrix) when the definition line: 127.0.0.1 localhost is missing from the /etc/hosts file. To make matters worse, /etc/htable does not automatically create a localhost line; you need such a line in /etc/localhosts. Since you were munging /etc/hosts, that's probably the cause. The problem is especially insidious because it doesn't show up until the next reboot. SWA