date: 1995/03/26 18:18:59; author: wpaul; state: Exp; lines: +23 -17
Make syslogd work again: in needs to be started in netstart right
before the rest of the system daemons are brought up and *after* the
network interfaces have been configured.
Also fix one other potential problem: the NIS services need to be started
relavively early since some of the other daemons might need them. The
automounter is a good example: if you use amd with NIS-based maps, you'd
better have NIS running before you start it. :) I think mountd might
need it too, now that netgroups can be read via NIS as well.
date: 1995/03/23 01:25:18; author: jkh; state: Exp;
Another pass through our rc files in an attempt to eliminate historical
crufy and generally make all of this easier to understand and modify.
1. Move all system configuration variables into /etc/sysconfig
2. Adapt other files to use it.
3. Add a host of new variables for micro-managing your system in various
ways. For 2.1, /etc/sysconfig will be machine-edited so that the user
doesn't even have to care at all about the various funny names we picked.
4. Enable dset. We won't get it debugged if we never use it, and no one
has said anything negative about it yet, so here goes!
5. Try to use one consistent style throughout.
- Do ntp right
- Move recenrly-added and long-standing junk from rc.local into rc, so
. that rc.local truly is LOCAL.
- Fix named invocation to use the correct boot file location.
1) ypserv is started with nis_serverflags, not yppasswddflags (that's what
I get for cutting & pasting without paying attention).
2) ypbind can also be started with arguments, so turn nis_client to
nis_clientflags.
Changed the everlenghtening list of "if [ -f /etc/hostname.foo ].." to a
loop which will do them all, and look for init-scripts for them as well.
perfect place to put your calls to slattach and such: /etc/start_if.sl0
for instance.
----------------------------
revision 1.8.2.1
date: 1994/04/18 06:37:29; author: rgrimes; state: Exp; lines: +10 -4
Use the hostname.* files created by the installation to reduce the
amount of work one has to do when setting up a system.
----------------------------
gives the flags to be passed to sendmail when it is started. (If it is
"NO", sendmail is not started.) Also, always start the portmapper regardless
of the value of $nfs_server; this should prevent the inetd complaints we
have seen from recurring.
