Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!bionet!ames!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.sys.sgi
Subject: Re: Linking /tmp to /usr/tmp
Summary: check /etc/rc[23]
Message-ID: <66228@sgi.sgi.com>
Date: 7 Aug 90 00:13:32 GMT
References: <9008061227.AA11480@aero4.larc.nasa.gov>
Sender: vjs@rhyolite.wpd.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 23

In article <9008061227.AA11480@aero4.larc.nasa.gov>, blbates@AERO4.LARC.NASA.GOV ("Brent L. Bates AAD/TAB MS361 x42854") writes:
> 
>     Also I can't find any scripts that execute RMTMPFILES, so it
> doesn't seem to be executed.


The nodes in /etc/rc[23].d are usually symbolic links to /etc/init.d.
The are run by /etc/rc[23], which are run by init when "changing state,"
as directed by /etc/inittab.

The SVR3 idea of the /etc/init.d files is to permit the old rc, rc.local, and
(on 3000's) other rc.* files to be divided by function, so that you can
install or remove things without hacking rc files, and can start and
stop portions of the system.

This stuff is partially documented in init(1M).  I recall reading the
AT&T words describing the general /etc/init.d scheme in some "Administrator's
Guide."



Vernon Schryver
vjs@sgi.com