Xref: utzoo comp.sys.sgi:7390 comp.unix.internals:1546
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!orc!inews!pima!bhoughto
From: bhoughto@pima.intel.com (Blair P. Houghton)
Newsgroups: comp.sys.sgi,comp.unix.internals
Subject: Re: Where does TERM get set for Telnet logins.(Solution!)
Message-ID: <1447@inews.intel.com>
Date: 18 Dec 90 16:27:39 GMT
References: <1990Dec17.034330.27909@ccu1.aukuni.ac.nz> <1990Dec18.041334.7498@ccu1.aukuni.ac.nz>
Sender: news@inews.intel.com
Distribution: comp
Organization: Intel Corp, Chandler, AZ
Lines: 11

In article <1990Dec18.041334.7498@ccu1.aukuni.ac.nz> russell@ccu1.aukuni.ac.nz (Russell J Fulton;ccc032u) writes:
>The moral of the story would appear to be Don't restart
>inetd from a terminal unless it is absolutely unavoidable.
>This probably applies to other daemons as well. If you do
>have to, then a boot of the system should be scheduled asap.

You could unset/unsetenv TERM before starting that daemon, though yes,
there could be other lurking environment hooks for this and other daemons.

				--Blair
				  "setenv VACATION Christmas"