Xref: utzoo comp.unix.i386:3468 comp.sources.wanted:10915 comp.protocols.tcp-ip:10542
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.i386,comp.sources.wanted,comp.protocols.tcp-ip
Subject: Re: Lachman TCP/IP on System V/386 has rsh, after all.
Message-ID: <1990Mar10.211002.11124@virtech.uucp>
Date: 10 Mar 90 21:10:02 GMT
References: <1U42U.Cxds13@ficc.uu.net>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 20

In article <1U42U.Cxds13@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>About the only thing missing from the nifty System V inittab scheme is the
>ability to easily set global environment variables for all one's daemons. Not
>that I'd want to go back to a random /etc/rc file again.

There is a way.  INIT reads the /etc/TIMEZONE file and processes all 
the 

	variable=value

records, placing the appropriate setting into it's (init's) environment which
will be passed to all child processes of init.

If you place too many variables into the file (and I don't know the count) 
init will just silently ignore the extra ones.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170