[1894] in SIPB-AFS-requests
Re: /afs/sipb/service/@sys
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Tue Mar 28 06:09:59 1995
From: mhpower@MIT.EDU
To: sipb-afsreq@MIT.EDU
In-Reply-To: "[1844] in SIPB-AFS-requests"
Date: Tue, 28 Mar 95 06:07:35 EST
>Is there any objection to getting rid of the ops service on the sipb
>afs servers and replacing it with another service that can be used to
>preserve our current configuration?
I haven't seen any replies to this, so I went ahead and created a
sipbops service; the files are in /afs/sipb/service/afs/mkserv.
(/afs/sipb/service/afs is a mountpoint for a new service.afs volume
which presumably will be used for files used on/by the afs servers
that aren't configuration files for individual machines.)
The main differences in the sipbops service (wrt the ops service) are:
-- Doesn't install a fixed inetd.conf file; instead, prints warning
messages for any enabled service that would've been commented out
in the inetd.conf installed by mkserv ops.
-- Similarly, prints warning messages if nsyslog.conf or elcsd.conf
isn't updated to use syslogger.mit.edu.
-- MRUPDATE isn't set to true
-- NOREMOTE=true, ERRHALT=false, AFSADJUST=false, SAVECORE=true
-- Since sipbops.add doesn't modify inetd.conf, nsyslog.conf, or
elcsd.conf, sipbops.del doesn't attempt to unmodify them.
-- sipbops.sync copies a few more files local than does ops.sync.
Examples are /bin/chpt, /usr/etc/kvar, and /usr/athena/bin/rcp.
I also tried not to break the Solaris support in the ops service,
although I haven't run the whole thing on a Solaris machine so I'm not
completely sure it would still work. In fact, I haven't run the whole
thing on any machine, although I think both ronald-ann and rosebud are
now consistent with what it would produce if it were run there.
Since the nsyslog.conf files should be stable now (i.e., there isn't
anything in /var/server/.services that would overwrite them), I've
reinstalled afs2sl.pl (see [1474]). Currently it's running on both
ronald-ann and rosebud. I added support for BosLog and VolserLog
(previously it had only read FileLog), added reformatting of fssync
and "Break call back" messages, and made a few other minor changes.
There is now a copy of this in /afs/sipb/service/afs/usr/local/bin
as well as in /usr/local/bin on ronald-ann and rosebud. As before,
if you're interested (i.e., want to get a filtered version of the afs
log files via syslog), you can subscribe to local4.info in the
nsyslog.conf file on charon, where the syslogs are forwarded.
Matt
